I am currently learning more about errors that can occur when migrating Update Sets in ServiceNow, and I would like to understand what happens when changes from different scopes are included in a single Update Set.
To verify the behavior myself, I prepared two ServiceNow instances and tried to migrate the Update Set between them. However, I was unable to complete the connection test successfully, so I decided to ask the community.
Scenario
I am assuming the following situation:
・Update Set scope: Global
・Changes included in the Update Set:
-Changes in the Global scope
-Changes in a Scoped Application
If I migrate this Update Set to another instance and perform the following steps:
Retrieve
Preview
Commit
what would happen?
My current understanding is that a Preview Problem would occur during the Preview step because of the scope mismatch, with an error similar to:
Update scope id 'xxxx' is different than update set scope id 'global'.
I assume that the Update Set cannot be committed until this issue is resolved.
Also, in this case, is it correct to understand that the Global changes and Scoped Application changes should be placed in separate Update Sets and migrated individually?
If my understanding is incorrect, or if there are any additional considerations regarding this scenario, I would appreciate your advice.
Thank you in advance.
