- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā06-10-2024 09:45 PM - edited ā06-10-2024 09:47 PM
Hi
I am trying to import update set from Dev instance to Test instance. The update set only contains Scripted REST API. When i import the XML and try to preview the Update Set, i get following error - "Could not find a record in sys_ws_definition for column web_service_definition referenced in this update".
Attaching the update set XML with this query.
Need help in resolving this error. I tried to just Accept this error, but if i do that, i can't find the API in the Test instance.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā06-10-2024 10:10 PM
seems something is not captured properly i.e. you don't have your main scripted REST API captured in update set but you are referring that in your customer updates
please check that
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
ā06-10-2024 10:10 PM
seems something is not captured properly i.e. you don't have your main scripted REST API captured in update set but you are referring that in your customer updates
please check that
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
ā06-10-2024 11:53 PM
Thank you for marking my response as helpful.
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
ā06-10-2024 10:17 PM
Hi @tanayapandit01,
I think you did the right thing by accepting it as has been explained here.
The important question is why you are not able to see the API after committing the update set changes to the test instance. In order to troubleshoot that, follow the steps mentioned in this article.
Commit an update set
Going through the update log should point towards something that didn't work as expected. Let me know if this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā06-10-2024 11:52 PM - edited ā06-10-2024 11:53 PM
Hello @Arpan Baishya @Ankur Bawiskar
Thank you for your response. I found the issue. It was with Update Set - I had only considered resource the within the API in the Update set not the main API. I assumed that only resource would be sufficient. Once I added both the API and the resource in the Update Set, there was no error while previewing or committing. The API is now appearing in the Test instance.