MRVS doesnt have value after submit

[jacobo]

Hi Experts,

I’m using MRVS and I noticed that sometimes the rows on the MRVS after submit the request is empty in the RITM.

I tried to search the in the MRVS values on the table sc_multi_row_question_answer but it's not there.

Do you have any idea what is happend?

Thank you very much 

Regards

[Barath P · Accepted solution]

Hi @jacobo 

• Clear the Cache:

  • Navigation cache.do
  • Press Enter to execute the command.
  • This action will clear the cache for your ServiceNow instance.

• Check Logs for RITM Creation or MRVS Errors:

  • Navigate to System Logs > All:
    • Go to the Application Navigator and search for "System Logs."
    • Select All from the menu.
  • Search for relevant logs:
    • Use keywords like the RITM number or MRVS-related variables to narrow down the search.
    • Look for errors or warnings related to RITM creation or MRVS processing.

• Verify Changes:

  • Refresh the ServiceNow application to apply the cleared cache and verify if the issue is resolved.
  • Test the MRVS submission again to ensure the rows are populated correctly in the RITM.

"If you found my answer helpful, please give it a like and mark it as the accepted solution. It helps others find the solution more easily and supports the community!"

Thanks & Regards,

Barath.P

[jacobo]

Hi

The issue continue and It just on PROD environment in others environments are working well. I have 6 MRVS on that catalog item. I didn't see any error on logs.

Do you have any idea how to resolvet it?

[Barath P]

Hi @jacobo ,

Do same thing which i have mentioned earlier. 

Check ServiceNow Updates

• Instance Differences: Ensure that your PROD instance is on the same version and patch level as other environments. Sometimes, differences in versions can cause unexpected behavior.

• Known Issues: Check the ServiceNow Community or release notes for any known issues related to MRVS or the sc_multi_row_question_answer table.
  
  

"If you found my answer helpful, please give it a like and mark it as the accepted solution. It helps others find the solution more easily and supports the community!"

Thanks & Regards,

Barath.P

[Pratik7]

We are also facing the same issue and have not found any root cause yet.

@jacobo  is it fixed for you ?