Migrate update sets only in Global scope but not Employee Center scope

[iamkurt]

I was capturing something in my Update Set and some content were in Global application scope whereas some content was in Employee Center application scope. The Update set automatically created a parent update set, and 2 more child batch update sets - one for Global application scope and 1 for employee center application scope. Now, with the benefit of hindsight, I realize creating catalog items/ topics and such other artifacts in Employee Center scope was a bad idea................

Is it okay to just load and commit the update set which has Global application scope?

[shyamkumar VK]

Hi @iamkurt ,

If you have different configurations in two different scopes and if you want to Move this to next instance , Create a Global Parent update set and add your other updatesets to this as child and migrate to next instance

[Hanna_G]

Hi @iamkurt 
It is most likely that you will need to commit both the global application scope and employee centre application scope update sets. 
This is because there will be updates in both that may be needed for the work that you have been doing. 
The easiest thing would be to commit the parent that has been created with the two child update sets. 

First step - Verify the updates in both child update sets to ensure you need them. 
Complete the parent update set which will complete the child ones too. 
Then retrieve the parent update set and commit on your next instance. 

More information about batch update sets are here: Update set batching

[S Goutham]

@iamkurt :
It's always recommended to create a catalog item and its related configuration based on the scope where the catalog will be used if its a custom application then in that same scope but most of them are created in global as this allow the us to call script and other functionality and deal less with cross scope privellage issue.

I would recommend recapturing the configuration to the global scope update set if the catalog item is not intended for a custom scope

The Employee Center scope intended scope is used for configure generic employee service center portal related changes and its realted data

As OOB feature now if you do not change the scope or use the "edit this record" on the info message and modify a configuration record on other scope system automatically creates a batch update set of where Parent update set will be Global and will contain other configuration in the respective child update set ot global and the other scope 

Hope this provides some clarification which you were looking for.