UI Policy Not Working on Existing Records

ddiroma
Mega Expert

I have a UI Policy that based on the selection of field a (Caused by Third Party) should show and make mandatory field b (u_third_party_name) within a problem record. This seems to work fine if it is a new record, but doesn't work at all on existing records. We just upgraded to San Diego. This is my first UI policy in San Diego. Any idea if I am doing something wrong or if this is a bug? I have done countless UI Policies this way, but maybe I am missing something.

find_real_file.png

1 ACCEPTED SOLUTION

ddiroma
Mega Expert

Looking at the dictionary history of the caused by third party field it seems as if someone changed the field type from a true/false checkbox to a choice list with True false. Although the records where the UI policy do not work were set after that field was changed, I am going to assume this has something to do with it. I am going to speak with the stakeholders, but I am guessing that I will end up creating a new field, passing the data, and deleting the old field. That is unless someone has a better idea/solution?

View solution in original post

6 REPLIES 6

SanjivMeher
Kilo Patron
Kilo Patron

Do you have that field 'Cause by third party' set on existing record?


Please mark this response as correct or helpful if it assisted you with your question.

Yes, it is currently set to true.

Filipe Cruz
Kilo Sage
Kilo Sage

Hello ddirona,

Can you check if the Caused by Third Party field is being set to True after saving the record?
And check also the client scripts to see if there is something there setting the field u_third_party_name not to be mandatory?

Best Regards,

Filipe Cruz

Hi Filipe,

Thank you for your response. The caused by third party was already set to true prior to the record loading. I checked history and nothing changed after saving the record. There are no client scripts running on either field. Both fields were recently created.

There is a UI policy on the Caused by Third Party where that field only shows if Function is Cloud Ops. That one is working properly. This one seems to work properly IF the original record Function is IT, that is changed to Cloud Ops, and the Caused by Third Party then gets set to true.


What is odd is if you set caused by third party to null/none, change the function back to IT and save, then try to do the same as Function = IT records mentioned in the previous paragraph. That doesn't work. I also turned off the UI policy for making Caused by Third Party Visible and it still doesn't work.