- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-20-2022 03:44 PM
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.
Solved! Go to Solution.
- Labels:
-
Problem Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-21-2022 10:14 AM
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-21-2022 10:14 AM
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-25-2022 08:53 AM
After creating a new field this worked, so it appears to be related to the change in the dictionary.