Pros /Cons of Merge and batch update sets

[Rithvik2]

Pros /Cons of Merge and batch update sets

[Rithvik2]

Thank you so much @Ankur Bawiskar 

Could you please give me clarity on this one also...from the above screenshot as Update Set 1 is the main[parent]......if we run that update set then child update sets will automatically run right?

so I had a doubt how the order goes....but you mention like we need to run individually...could you please give me clarity on this...

[Mark Roethof]

Hi there,

Don't know any cons on this. One advantage would be having to publish only the parent update set, so a lot easier/quicker to deploy.

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark
2020 ServiceNow Community MVP
2020 ServiceNow Developer MVP

---

LinkedIn
Community article list

[Rithvik2]

@Allen A @Paul Morris @Mark Roethof @Ankur Bawiskar 

I have created a batch update set for the below mentioned requirement...

Created 1 global update set assigned to 4 child update sets...[parent-child relationship] in dev environment and moved to test environment..

After moving we came to know that we need to do some more development...so in this case how can I proceed? with the same batch update set? is it possible?

[Ankur Bawiskar · Accepted solution]

Hi,

you can create separate update set in dev;

since you already moved batch1 containing 4 update sets to test; move this single update set to test

then for migrating from test to prod you can set parent for this new update set as batch1 so that when Batch1 moves to prod from test it will have 5 update sets

Regards
Ankur