Mandatory description is becoming empty after mapping to the table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2024 10:20 PM
Hi Everyone!
I have created a record producer and there is only one field is mandatory which is description.
But sometimes users are able to submit that request without filling that, or maybe somehow after submitting the request, in the table, that description field becomes empty. I have mapped that field correctly, still this issue persists.
Let me know if you have any insights on this!
Thanks in advance,
Amol
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2024 10:54 PM
Hi @Amol Pawar ,
It should not happen, as you have maid mandatory at attribute level. Do one more thing add one catalog ui policy to make field mandatory instead of making them at attribute level.
-------------------------------------------------------------------------
If you found my response helpful, please consider selecting "Accept as Solution" and marking it as "Helpful." This not only supports me but also benefits the community.
Regards
Runjay Patel - ServiceNow Solution Architect
YouTube: https://www.youtube.com/@RunjayP
LinkedIn: https://www.linkedin.com/in/runjay
-------------------------------------------------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2024 11:16 PM
Hi @Amol Pawar ,
It should be Mandatory because always mandatory at variable take precedence so no non mandatory from ui policy or client scripts will impact.
Description field empty check any client scripts in in target custom table is configured which is clearing value.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0787280
If my response helped, please mark it as the accepted solution ✅ and give a thumbs up👍.
Thanks,
Anand
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2024 11:32 PM
Hey Amol, try making an Catalog UI policy for it. Also if you think the problem is arising due to mapping, i would suggest you map the two fields via scripting, see if that works.