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?

[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

[GlideFather]

Hi @iamkurt,

good practice is to have a global update set as parent, then you have any other scopes under it.
You just need to have the particular scope as current to update the parent field for the child one.

Does it make sense? If not, let me know and I will try to reformulate my point :)))