Proper method for batching update sets

[kdelbridge]

I have a story that I have multiple update sets for, 7 to be exact.   When it comes time to retrieve and commit these to PROD, I'd prefer to not have to commit these individually, although I can.

I have read many articles where batching the update sets is preferred over creating a merged set.

If I do "batch" these, what is the best practice?

Would it be best to open the update set that will be the Parent (1st one created) and then just add update sets for versions 2 - 7 via the Child Update Sets related list on the Parent record (version 1)?

OR - is it best to create a Blank update set, name it Batch, following by proper naming convention for my story and then associate all update sets for the story via the Child Update Sets related list on my newly created Batch update set?

I appreciate in advance any advice provided.

[Ankur Bawiskar]

@kdelbridge 

create 1 parent update set in Global scope

Then add your other update sets as child for above

then migrate the parent

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Dr Atul G- LNG]

Hi @kdelbridge 

Batching is best practice, but make sure that when you commit, the commits are in sequence so that one child update set does not overwrite the changes in another update set.”

One. more: https://www.servicenow.com/community/developer-forum/servicenow-update-set-batching-best-practices-l...

https://youtu.be/LjD4YQhbygc