What is the difference between batch update sets and merge update sets
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-08-2020 11:03 AM
What is the difference between batch update sets and merge update sets and
what exactly batch update set will do and what merge update set will do?
Can anyone explain in simple words

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-08-2020 11:05 AM
Hi,
Batch update sets contain a parent child relationship where the individual updates stay within the respective sets: https://docs.servicenow.com/bundle/orlando-application-development/page/build/system-update-sets/hie...
Merge update sets take all updates from selected update sets and puts them all in 1: https://docs.servicenow.com/bundle/paris-application-development/page/build/system-update-sets/task/...
It is advised to use Batch update set.
Please mark reply as Helpful/Correct, if applicable. Thanks!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-08-2020 11:14 AM
Just to add to that...
The Update Set Merge capability has existed for a long time. Batch Update Sets are a newer feature.
One of the challenges with merging update sets is that there is no way to "undo" a merge.
With Batch Update Sets you can add a parent or remove a parent. You can move a child from one batch to a different batch. The child Update Sets retain all their identifying information. It is much more flexible and forgiving.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-08-2020 11:22 AM
Hi,
When you merge into an update set all changes are moved into the same update set and when you create batch child relationship you are not merging the changes into one update set, you are building a parent-child update set hierarchy. So it's easier to identify changes/versions into batch hierarchy than merged update set because all changes and versions are combined.
The most relevant thing it's when you need to back out some specific change or update set. If you have created a merge you are not going to be able to just back out some specific change or update set, you need to back out the entire merged update set.
Here's some useful link about back out:https://docs.servicenow.com/bundle/orlando-application-development/page/build/system-update-sets/task/t_BackOutUpdateSet.html#t_BackOutUpdateSet
If it was helpful, please give positive feedback.
Thanks,
☆ Community Rising Star 22, 23 & 24 ☆
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2020 03:00 AM