Dependent Dropdown Question

[Lindsey_Lindow]

When users add new rows to an automotive repair app, dependent dropdowns are used for [MAKE] and [MODEL] selections, so if users select "Audi" as [MAKE}, they will only be shown model names of Audi vehicles (same with all other make/model combinations). I'd like to avoid having to manually add newly released model names to the backend sheet every year by allowing other values, as allowable in Enum columns. Is this possible with dependent dropdowns?

[WillowMobileSys · Accepted solution]

Yes,  There is a property to "Allow other values".  You simply need to turn it on.

HOWEVER, you may soon regret it.  Giving users the freedom to enter their own value leads to other problems with spelling and syntax.  For example, let's say one user enters "Chevrolet"  while another enters "Chevy".  You will end up with rows with different values that impact searching or even selection lists.

My Suggestion....Use utility tables to provide the list of dropdown values.  Then create "maintenance" views to add/update these utility tables and maybe give access to only a select few.  This way you can add new values directly from the app BUT most importantly control the spelling/syntax of these new values so they are consistent throughout the app.  Yes, you would still need to add these yearly if that is your current process BUT you would not need to go to the datasource to do it.  The biggest benefit is consistent AND complete data across the app.