There are times were we have to work with multiple application scopes in ServiceNow. There are usually no problems with this.
But a problem might arise during the migration of update sets to another instance (for example from UAT to Prod).
The following error might be encountered: Cannot commit Update Set – Update scope id is different than update set scope id ‘global’
This problem usually occurs when you are being asked the following question (or similar):
Clicking “Click here” is convenient, but will create an update belonging to one application scope in the update set of another application scope, thus throwing the error when trying to commit/preview the set.
To fix the conflicts after you encounter it, the updates in the wrong application scope needs to be move manually to an Update Set with the correct scope, or you can export the update set to XML and modify update set IDs in the XML.
To prevent these conflicts, you will have to refrain from using the “Click here” button above. To do this, you will have to create the proper update sets in the first place – at least one for each application scope you are working on. During development, you will have to keep switching update sets to make sure that the updates are going into the correct update sets. This might increase development time slightly, but it will reduce headache during migration.