Update Sets - Parent/Child Relationship?

Justin W · ‎07-19-2021

Hello,

I had a quick question regarding Update Sets? I have pushed something from Dev to Test and realized that I missed making a change.

Am I able to just switch that Update Set back to "In Progress" and make changes?

Also, does anybody know about Parent/Child Update Sets in case I wanted to create a new Update set?

Thanks in advance,

Justin

-O- · ‎07-19-2021

Just to clarify, batching is not linked with moving update sets, but with committing them.
So there is no such thing as batch migration. It is true that if you batch up a bunch of update sets in Test and commit them in a single batch, all those will be moved together into Prod (or other instances). But that is done automatically by the system, not by you. Furthermore, once the update sets end up in Prod, you can add further update sets to the batch before committing. Say in Test you realized you need to fix something and you have created "Update Set 4". You move it to Test, commit it, than you move everything into Prod (or any other instance). You will end up with 4 update sets, 3 in a batch 1 solo. You can now add that solo one too to the batch, and again commit all in one go.

Also it does not matter how you commit and how you move update sets between instances, because all that matters is the destination. You batch there when you want to commit - that's the beauty of batching.

View solution in original post

Mark Roethof · ‎07-19-2021

Hi there,

"Am I able to just switch that Update Set back to "In Progress" and make changes?"

No. As you mention you already pushed this to the next environment. You will have to create a new Update Set, add a suffix (B) or (2) for example to make clear that it is for the same change, though a follow-up update set due to a bug/fix/follow-up.

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

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

---

LinkedIn
Community article, blog, video list

Kind regards,

Mark Roethof

Independent ServiceNow Consultant

10x ServiceNow MVP

---

~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field

Justin W · ‎07-19-2021

Hi Mark,

That is helpful. Do you know at all about Parent/Child Update Sets. A colleague mentioned it but I am newer to using Update Sets.

-O- · ‎07-19-2021

It is called batching. When you need to commit several update sets, in the target instance you pick one Update Set and make it the parent for all other updates sets to be committed. Then you verify and commit that sole parent Update Set*. It helps in automatically picking the newest update for each modified record included in the update sets.

*) That does not mean that only the parent update set will be committed; all will.

Justin W · ‎07-19-2021

Hi Janos,

Thank you for the reply. In my situation I made the changes in Dev and then pushed them to Test. So then my original update set in Dev would be the target/Parent for the batch migration?