MRVS information getting removed once task form is saved
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2025 04:49 AM
Hi Community,
I am facing an issue where if one of the client script (calling script includes too) is running, then the records where MRVS is stored ['sc_multi_row_question_answer'] is dissapearing.
Are there similar issues faced by anyone else, and is there a workaround for this issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2025 05:33 AM
We dont have any other MRVS which we could test, but yes, i coud confirm that value is coming in to multi row question answer table. after sctask table is updated, the data is cleared.
There are no other scripts that are clearing the multi row question answer table, which i have already checked the instance (for BR and CS)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2025 05:35 AM
if this is DEV instance no harm in creating a new MRVS in same catalog form and see how it behaves
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
03-12-2025 11:31 PM
Did you find the root cause of this?
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2025 11:53 PM
Hello @jnt-cnt,
Could you please review the flow for the respective catalog item?
After the catalog task is updated, please check the next action in the flow.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2025 11:58 PM
HI @jnt-cnt,
if you are using clear value in client script. this issue will occur. please check the client code once.
Thank you.