
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2019 02:50 PM
Just loaded an update set from our dev instance to test, with 3 new catalog items. For two of the items I get this when I try to access them from the portal:
The third catalog item is using the SC Catalog Item widget just fine. What gives here?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2019 08:35 AM
Here's what I managed to suss out. After examining the variables contained within the catalog item, I found that 2 were essentially pointing to places that hadn't be translated over by the update set. One was a List Collector that was pointing to a non-existent List Table (Type Specifications tab), the second was a Macro that was pointing to a non-existent Widget (Default Value tab).
After manually pulling this data over via exported XML files, things came around. I'm 95% sure this was it, although I didn't confirm (via logs) that these were the explicit things which caused the errors to be thrown.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2019 08:35 AM
Here's what I managed to suss out. After examining the variables contained within the catalog item, I found that 2 were essentially pointing to places that hadn't be translated over by the update set. One was a List Collector that was pointing to a non-existent List Table (Type Specifications tab), the second was a Macro that was pointing to a non-existent Widget (Default Value tab).
After manually pulling this data over via exported XML files, things came around. I'm 95% sure this was it, although I didn't confirm (via logs) that these were the explicit things which caused the errors to be thrown.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-17-2024 10:31 AM
In my case, we had the option to select four items in the 'Describe Needs' section of the order guide. The order guide worked as expected for three items but not for the last one. The reason for that was due to not having a workflow or flow assigned to the last item. So, everytime we clicked on 'Next' button we got an error. The fix was to assign a workflow for that item. The order guide would then work as expected.
These articles may be helpful too:
- https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0754339
- https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1640974
- https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1113665
- https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0685163