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

[Artemis15]

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

[Tyler Hoge - Gl]

Let me know if this works or not.

navigate to your update set

[nikhilnishant]

Thanks. This Works!

[abdulmominkhan]

Hi,

Solution proposed by Tyler Hoge will work. There is one alternate also. Migrate your application name from development to test and production.

Create one update set on   development and make your current update set and follow the steps

1. Go to System Applications --> Application (left hand navigation)

2. Select the application that is giving error in test or production instance

3. Open that application

4. click on update (provide short description)

5. Save and close.

6. Now migrate update set to Production or TEST instance.

7. Once your application has been moved, your update set which are giving error will not throw error.

[Suman9]

Thanks Tyler, it worked by changing Application Scoping !

[bharath10]

Hope you guys are doing well.

Thanks for sharing information.

i am curious about how changing of Scope will impact during instance upgrade OR any other impact application function, which was there before we changed it to Global. Or will it hamper any platform, that particular functionality.

please shed some lights on this.

Thanks in advance.

R's,

Bharat