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

[Pradeep Sharma]

Hi Akash,

Based on the error it looks like the customer Updates global got captured in your scoped app. In this case Customer Updates with the wrong application should be manually moved to an Update Set with a correct scope.

Mostly this should be related to the form sections.

[Venkateswarlu K]

Hi

ctomasi   and pradeepksharma   Good day!!!

Is there any API used in update sets while retrieving the completed   update sets from the source instance???

if Yes what type of API it is???

[Chuck Tomasi]

All the 'magic' that happens with retrieving update sets happens in the UpdateSetAjax script include.   It appears to use the GlideRemoteGlideRecord API. You can dig in more here.

(change YOURINSTANCE in the below URL to your instance name or search for the UpdateSetAjax record in System Definition> Script Includes)

https://YOURINSTANCE.service-now.com/nav_to.do?uri=/sys_script_include.do%3Fsys_id%3Db71e40d60a0a0b5...

[Venkateswarlu K]

Hi Chuck

Thanks for ur fast replay

That was amazing trick chuck!!

The same thing will happens in team development application   also ??

am i correct???