Dropdown list: It needs to be kept that the default variable from the XML even if it doesn't exist in the `options` in the definition.

Is your feature request related to a problem? Please describe.

I’m always lost my default variable from XML if it doesn’t exist in the options in the definition.

Describe the solution you’d like

Pin the default variable top even if it doesn’t exist in the present options definition array.

Describe alternatives you’ve considered

Read the default from the XML ==> options.unshift(default variable) ==> render the dropdown component

[nickvaras]

I was referring specifically to non-variable values in dropdown fields. For my application I ended modifying the function class validation function to just add missing values to the list of options, so for now the suggestion can be ignored. I’m aware of the dynamic lists functionality and that’s probably the proper way to accomplish this.

What you say about the change taking place a few years ago is accurate, I just hadn’t updated the library for a while and when I did that change caused some problems.

Thank you for taking the time to answer!

[maribethb]

We’re going to continue to require that the selected value in the (built-in) dropdown field is valid, so we’re not planning to implement this feature request. You can work around this by either using the dynamic dropdown options, or doing as you’ve done and create a subclass of FieldDropdown that behaves as you want in the validator.