Choices depending on dot-walked values not filtered without saving the form or having the dot-walked field placed on form - Known Error

Choices depending on dot-walked values not filtered without saving the form or having the dot-walked field placed on form Description Choices depending on dot-walked values not filtered without saving the form or having the dot-walked field placed on the form

Steps to Reproduce

Create a Choice field on the Incident table 2. Make the field dependent on caller_id.last_name 3. Create some choices for the field. Set their dependent values to the last_name value of some users. We found 'Tuter' and 'Dyckman' are the simplest examples (Abel Tuter, Charity Dyckman) 4. Test the choice field on the form.

You will see that the choices are not filtered according to the user set in the caller_id field unless we save the form. To make the choices filtered immediately after changing the caller_id, you need to put the dot-walked field 'caller_id.last_name' on the form. Workaround After carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to not address this issue in any current or near future releases. We do not make this decision lightly, and we apologize for any inconvenience.

The workaround for the issue is to put the dot-walk field on the form and then use a UI policy to hide it.