A persistent Reference-type custom field validates correctly against an LOV, but users want to be able to free-type into the field instead of always picking from the list, since the LOV takes a noticeable time to load and they use this screen constantly — is there a way to validate against a list of allowed values without forcing LOV-only entry?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Not with a Reference-type field specifically — that type inherently requires picking from the LOV, with no free-typing option. Instead, create the custom field as a plain persistent Text-type field (so users can type freely, with no LOV lookup delay), and add a Custom Event triggered on insert/update that validates the entered value against your allowed list, raising a blocking error (for example, via Error_SYS.Record_General) if it doesn't match. This gives you the fast free-typing experience the users want while still enforcing the same validation at save time that the LOV would have provided.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions