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

[aquarilis]

adding my few cents:

I have figured out that this is happening when you are being asked the following question " This record is in the [remote scope/app] , but [current scope/app] is the current application. To edit this record click here.

As convenient as the "click here" option is, what it does is create a customer update in your current update set, but the customer update would point to another application, thus throwing the error when trying to preview/commit the update set.

(such a shame that this system is not made more thoroughly… but at least, it's not potentially sending the customer update into the default update set in that other application).

[Ravi151]

Hi aquarilis,

I have a similar issue Cannot move update to a set for a different scope. 

Customer Update

sys_search_context_config_e1a2c1962f1780108490dcb6f699b610  .

I want to move scope from default to Ydc which is a private scope .

Have no clue how to do this .

[Chris P_]

So obviously they still didn't change this and people (like me) still use the "click here" option.

And now I'm stuck with an update, in my scoped update set, which needs to be transferred to an update set in Global, because I need this update (and I know there are/will be others) to transfer to my Test- and Production-environment.

But when I try to change the updateset on this record to a global one, the system tells me: Cannot move update to a set for a different scope.

So I can put an update for a Global record in my scoped updateset, but I can't remove it, nor can I import it into other environments.

Why on earth is this crappy function still available?!?!?

[Jon23]

This is the solution I used to fix a similar issue not fixed by previous suggestions in this thread.  Hopefully this will help others 🙂

ServiceNow Version: Madrid Patch 4

My Scenario:

• Created a scoped update set
• Captured one scoped Customer Update
• Update set complete
• Clicked the 'Export to XML' link (link only appears when State=Complete)
• Imported XML file to another instance
• Appeared under 'Retrieved Update Sets'.
• Previewed failed ...update scope id is different than update set scope id 'global'...

When I opened the XML I noted the following info was blank:

<application display_value=""/>
<application_name/>
<application_scope/>

• Updated the values in XML file to the application scope (used 'sys_scope.list' to get info):

<application display_value="Service Catalog Service Portal">37c5cea187233200e0ef0cf888cb0bb8</application>
<application_name>Service Catalog Service Portal</application_name>
<application_scope>sn_scportal</application_scope>

• Saved XML
• Imported XML
• Preview Successful
• Committed

All working as expected 🙂

[Ravi151]

Hi  jwalton,

I have a similar issue Cannot move update to a set for a different scope. 

Customer Update

sys_search_context_config_e1a2c1962f1780108490dcb6f699b610  .

I want to move scope from default to Ydc which is a private scope .

Have no clue how to do this .

any suggestion is appreciated .

Thankyou ,