- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-19-2021 07:57 AM
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
Solved! Go to Solution.
- Labels:
-
Multiple Versions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-19-2021 10:03 AM
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.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-19-2021 09:53 AM
Depends. What is your path for getting your updates to prod? Is it:
dev > test > prd
or
dev > test AND dev > prd
If dev > test AND dev > prd, you can for example retrieve your fix update set on test, and then on dev still attach it to a parent. When retrieving on prd, everything will be retrieved in one go, everything can be commited in one go, etc..
Obviously, disadvantage is that this is not 100% the same as you applied your changes from dev > tst.
If dev > test > prd, you could also retrieve your fix update set on test, and on test apply the parent. Then again, when retrieving on prd, everything will be retrieved in one go, everything can be commited in one go, etc..
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-19-2021 09:54 AM
No, you do the batching in the target/destination, in your situation - Test instance.
So you create an update set "Update Set 1" in Dev and move it into Test. Then you realize you missed something. You create another update set in Dev, "Update Set 2". Move that one to Test too. Then you need to do further updates so you create "Update Set 3" in Dev and move that one into Test too.
Now you have 3 update sets in Test (and feel you are missing nothing, so you'd like to commit those).
So the batching begins, you pick one (doesn't matter which one) - say "Update Set 2" and make it be the parent of both "Update Set 1" and "Update Set 3".
Now you have all 3 batched.
All that remains is to open "Update Set 2" - the parent and verify and commit.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-19-2021 10:03 AM
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.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-19-2021 09:51 AM
Batch update sets do have more advantages. It's not just parent/child, and having all update sets automatically closed, retrieved to other instance, and only the parent needs to be previewed and committed.
For example, one of the big other advantages:
- Working with different application scopes! For example your parent and one or more child can be in global scope, while other childs can be in different scopes. Works perfectly!
Also see this docs page:
https://docs.servicenow.com/bundle/paris-application-development/page/build/system-update-sets/hier-...
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

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-19-2021 09:40 AM
Hmmm your colleague mentioned update sets though didn't tell you anything 🙂
Is it a question in general about update sets and parent/child? Or if you can still apply this on your update set, which is already retrieved on test.
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