Merging Completed Update Sets

[kurtbell1]

Is it a bad practice to merge Completed Update Sets?   Doesn't seem like it - but the default filter in the Merge utility only returns In Progress update sets. I realize I can change the filter it just seems like ServiceNow is suggesting you only do this to Update Sets that are In Progress and was wondering why.   Anyone have thoughts on the matter?

[Rajesh Mushke]

Hello kurtbell

Yes Merge Update set feature is a much used featured. It work very simple you will have to select your update sets in status "In Progress" then just click to merge them.

Once it is done you will have a single update set with all the updates of those 10 captured in it.

Best Practices post Merging

1) Once done go to those 10 update sets and click on an option called as "Do not trasnport" so that those won't be merged again later.

2) Also you should change the status of those 10 update sets from In progress to either Ignore or Complete whichever you feel comfortable/manageable.

PS: 10 is just an example. you can select as many you want.

Please mark answer as correct, if it was really helpful 🙂

Check this link

https://docs.servicenow.com/bundle/geneva-custom-application-development/page/build/system_update_se...

Update Set Merge

how to select completed update sets to be merged?

http://wiki.servicenow.com/index.php?title=Update_Sets_Best_Practices#gsc.tab=0

[sndangibbard]

Kurt

If you are working with the Jakarta version of the platform I would urge you to consider batching your update sets rather than merging:

https://docs.servicenow.com/bundle/jakarta-application-development/page/build/system-update-sets/hie...

[Brian Arndt1]

If you're working with large numbers of update sets (between about half a dozen developers, we typically install 30+ sets every other week), merging still seems a better choice over batching due to this feature of merging:

The most recent change for each object is moved from the original sets to the new set. Only changes that are not merged into the new set remain in the original sets. A message indicates how many updates were moved and how many were skipped. For example, if both update sets modify the Incident form, only the most recent change is moved to the new update set. The other modification remains in its original update set to provide a record of the changes that were not moved.

After we went live with Jakarta, we tried the batching feature and unexpectedly discovered we had to choose which updates to accept based on which was newer. When batching gets this feature, then it will be the preferred method for us.

[Community Alums]

You can reopen your Update Safely using this Utility:
https://developer.servicenow.com/connect.do#!/share/contents/3673648_copy_update_set?v=1&t=PRODUCT_D...