Multi-row variable set value is being cleared when it is made read only
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-26-2020 12:42 PM
I've got catalog item which contains multi row variable set. The multi-row variable set is being displayed on the RITM and SCTASK variable as read only.
I have created UI Policy to make the variable set read only on RITM and Task forms. but when i perform any update operation on the RITM or Task, the variable set value is getting cleared out.
If i deactivate the UI Policy and then perform update operation on RITM or Task form, then the value is not getting cleared out.
clear variable value is also set as false in the ui policy.
Has anyone faced this issue or anyone can assist on resolving this issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-26-2020 01:47 PM
Hello Arvind,
Just a couple of items for consideration:
1) Have you tried watching the variable (right-click > watch variable) and then observe what populates in the Javascript log and field watcher at the time that the data clears out? Curious to see if there could maybe be another UI Policy or OnChange Client Script that could be activating, that'd be worth factoring into your troubleshooting.
2) Can you post a screenshot of your UI Policy in its entirety (not just the actions related list) so we can see if anything else leaps out from that?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-26-2020 02:27 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-26-2020 02:31 PM
Are there any UI policies or client scripts defined within the variable set itself?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2020 07:57 AM
Thanks for the additional screenshots, Arvind.
One more minor thing, just for kicks...
If you disable this UI Policy, and then perform the same steps that lead to the data in the field being cleared, does that still occur?
The thought here being to have certainty that the behavior is connected to when this UI Policy is actively in use.