Dropdown choiceValues and values

1. Never remove values from the database. Use a Boolean flag (typically labelled 'isActive') to indicate whether the value is currently available for use
2. Always store the key to the value, not the value itself. Keys are immutable and, if you follow the previous guidance, always available
3. For new Cases you can exclude those values in the Ref Data that have 'isActive' marked as 'false'. Cases that previously used that value can have that value (and its key) appended to the currently active list to prevent UI failures.
4. Have very clear rules that determine if a Case that has a value that has an inactive value selected and is now being edited can continue to use that value or that it needs to be replaced with a currently active value. This will be driven by the business requirements. 

1. Never remove values from the database. Use a Boolean flag (typically labelled 'isActive') to indicate whether the value is currently available for use
2. Always store the key to the value, not the value itself. Keys are immutable and, if you follow the previous guidance, always available
3. For new Cases you can exclude those values in the Ref Data that have 'isActive' marked as 'false'. Cases that previously used that value can have that value (and its key) appended to the currently active list to prevent UI failures.
4. Have very clear rules that determine if a Case that has a value that has an inactive value selected and is now being edited can continue to use that value or that it needs to be replaced with a currently active value. This will be driven by the business requirements. 

Good stuff, and good to spell out more explicitly.

Witold Wozniak said:

"Now a way to fix it with the text data is to check if the data is present in the choiceValues and if yes, then only show it in the value else show null."

I guess this would be a way to prevent the evaluation error, but I think it would be up for debate to decide whether a blank dropdown is even worse than evaluation errors, since they are easier to miss, and errors usually force quick fixes. Am I reasoning correcly?

I'm with Harshit, I almost always configure my dropdowns to check if a value is present in the options, if not, show null.  I can't think of any case where it would be better to have an evaluation error rather than a blank dropdown selection - with a required flag, the user will be forced to choose a new value during submit/resubmit. 

a!localVariables(
  local!options: { "A", "B", "C" },
  local!selection: "D",
  a!dropdownField(
    label: "Options",
    placeholder: "--Select--",
    choiceLabels: local!options,
    choiceValues: local!options,
    value: if(
      contains(local!options, local!selection),
      local!selection,
      null
    ),
    saveInto: local!selection,
    required: true
  )
)

Somewhat agree all pink = bad.

However, I would avoid a band-aid that prevents the underlying problem from getting solved.

However, blank spaces on a dropdown are such glaringly obvious bugs I could scarcely imagine a scenario where fixing it wouldn't be top priority for business, so band-aid would never keep it from getting fixed.