- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2023 04:27 AM
When previewing my update set I get the following error: "Cannot commit Update Set 'UPS - SSW - Human Resources - STRY0248851 - Quick Links - 1(EmCtrEx)' because: Update scope id 'global' is different than update set scope id '9f678ed6c3003010069aec4b7d40ddba'. Resolve the problem before committing."
There should not be a need to change the application scope when retrieving and previewing/committing update sets. The sys IDs for the 'Global' application scopes in my Dev and Test instances are the same. These update sets were created in the 'Employee experience taxonomy' application scope. The sys IDs for this scope is the same in both my Dev and Test instances. The sys ID listed in the error is the sys ID for the 'Employee experience taxonomy' application scope.
Can someone help with how to resolve this issue? Thanks... 🙂
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2023 05:56 AM
@Sharon Williams ,
Please check the Application name in the "customer updates" of your update set, as mentioned below in the screenshot.
All the updates should be related to the "Employee experience taxonomy", their might be an update present which is related to the "global" application, remove that entry from the update set and try again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2023 05:56 AM
@Sharon Williams ,
Please check the Application name in the "customer updates" of your update set, as mentioned below in the screenshot.
All the updates should be related to the "Employee experience taxonomy", their might be an update present which is related to the "global" application, remove that entry from the update set and try again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2023 05:59 AM
You have to change the scope to retrieve the scoped updated sets.
Please refer to this article for more information - https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0862487

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2023 06:11 AM
Hi @Sharon Williams ,
@Mark Roethof has explained beautitifully in this article to understand and fix this : https://www.servicenow.com/community/developer-articles/detecting-quot-update-scope-id-is-different-....