Mandatory description is becoming empty after mapping to the table

Amol Pawar
Tera Guru

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.

AmolPawar_0-1734589118892.png

Let me know if you have any insights on this!

Thanks in advance,

Amol

3 REPLIES 3

Runjay Patel
Giga Sage

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

-------------------------------------------------------------------------

In this video i have explained about Web service integration in ServiceNow like how it works, how we can configure it, what are the prerequisite and many more. I have covered below topics in this video. 1. understand Web Service. Like when and how we will use it. 2. Talked about Inbound and ...

Anand Kumar P
Giga Patron
Giga Patron

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

yuvarajkate
Giga Guru

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.