Field value showing in XML but not on form
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-11-2025 04:07 AM
I am populating a form field value through an Update API but its saving the value in the backend but not showing on the form.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-14-2025 03:15 AM
Hello @Sachin bagyal ,
Thanks. This is the correct format for a Date field. Just to make sure: the single quotes (') are not part of the XML, correct?
Have you checked if there are any Client Scripts or UI Policy Actions that might clear this date field when the form loads?
What if you are updating this with a date manually (not via the API). Will the value show on the form after saving?
Regards,
Robert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-14-2025 03:26 AM
then definitely some script etc is clearing it on form?
Check the points mentioned by @Robert H
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-11-2025 04:16 AM
Can you check the field type. If it is choice/reference value please check incoming value matches with ServiceNow backend value.
--
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-11-2025 04:58 AM
are you populating it with the correct value?
share how that API is pushing the data and how it looks in XML and on form
share some screenshots.
If my response helped please mark it correct and close the thread so that it benefits future readers
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-14-2025 04:33 AM
Thanks all for your suggestions, the issue was fixed It was a UI policy script which is clearing that value.