Cannot commit Update Set :Update scope id is different than update set scope id 'global'

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2015 12:52 PM
Hi
I'm getting below error.
We take backup from our dev instance and cloned it from Prod. Our dev instance was just upgraded to Fuji and we are creating a new application (not via application module).
We have taken backup using update set but after cloning, when we are trying to load update set than we are getting following error.
Cannot commit Update Set because: Update scope id '811e4bc56f8f31005de9f00dba3ee4fc' is different than update set scope id 'global'. Resolve the problem before committing.
Please help me on this.
--
Cheers,
AR
- 41,383 Views

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-22-2024 07:11 AM - edited 04-22-2024 07:11 AM
Hello @Artemis15 ,
1.Create an update set in another (Test) instance in the local update set . Make sure to use the application scope as (811e4bc56f8f31005de9f00dba3ee4fc) mentioned in the error. Complete the blank update set and export it.
2.In the DEV instance , go to "Retrieved update set" and import XML of the update set.
3. Then open the customer update having error and change the "Remote update set" with the one you have created in step 1.
4. Preview and Commit the update set.
5. In previous update set you can skip the customer update as you have already captured the update in newly created update set.