UpdateSet Commit Order

[d-aizawa]

Hi.

I am planning to create multiple UpdateSets and commit them to the validation environment.

I had one question, If I create multiple UpdateSets, how do I commit them to the validation environment?

Commit in order from the oldest UpdateSet creation date?

Or commit from the oldest update date of the contents recorded in each UpdateSet?

Does anyone know about such UpdateSet Best Practices?

Also, if there is a description in the official document, please cooperate.

Thank you!

[Mark Manders]

Depends. Are you 100% sure you did not touch the same object in 2 update sets? In that case you can commit them in any given order, but if you are not, create a parent update set and attach all others to it. Move that parent to the next instance, preview and commit. It will get the latest version of each object on your instance.

Merging is another option, but you can never unmerge if you run into any issues. And you can detach update sets from a parent.

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

Mark

[Ankur Bawiskar]

Hi,

You can use the Batch feature while migrating update sets to next environment instead of dealing with migrating them one by one.

It provides great capabilities and you need not worry on the sequencing.

Remember you can create batch of update sets which are in same scope only.

Update set batching

How to create a batch update set in ServiceNow

ServiceNow Update Set Batching - Best Practices & Lessons Learnt

Regards
Ankur

[Ankur Bawiskar]

@d-aizawa 

Hope you are doing good.

Did my reply answer your question?

If my reply was informational mark "helpful" or if it is justified mark it as the "Correct answer".

Regards
Ankur

[Ankur Bawiskar]

@d-aizawa 

Hope you are doing good.

Did my reply answer your question?

If my response helped please close the thread by marking appropriate response as correct so that it benefits future readers.

Regards
Ankur