Need guidance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2024 02:15 AM
Hi All,
I have 50 update set ,I want to deploy these update set into test instance .
Please what should be best approach
batch update
Merge Update
If i go with merge ,then will i be able to revert changes for a particular update in test instance

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2024 02:38 AM
@Ketan Pandey Dealing with multiple update sets can lead to problems, including committing update sets in the wrong order or inadvertently leaving out one or more sets. You can avoid these problems by grouping completed update sets into a batch.
o revert an individual update set from a batch update set in ServiceNow, follow these steps:
-
Identify the Update Set:
- Go to System Update Sets > Local Update Sets in the application navigator.
- Search for the update set that was part of the batch update set you want to revert.
-
View the Update Set:
- Open the specific update set to view the list of changes.
-
Manually Revert Changes:
- For each entry in the update set (like a Business Rule, Script Include, etc.), you need to:
- Navigate to the affected record (such as the Business Rule or Client Script).
- Check the previous version using the Versions related list at the bottom of the form.
- Revert the record to the desired previous version by clicking on the Revert to this version icon.
- For each entry in the update set (like a Business Rule, Script Include, etc.), you need to:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2024 04:34 AM - edited 09-29-2024 08:55 PM
@Sandeep Rajput SpotifyPie wrote:@Ketan Pandey Dealing with multiple update sets can lead to problems, including committing update sets in the wrong order or inadvertently leaving out one or more sets. You can avoid these problems by grouping completed update sets into a batch.
o revert an individual update set from a batch update set in ServiceNow, follow these steps:
Identify the Update Set:
- Go to System Update Sets > Local Update Sets in the application navigator.
- Search for the update set that was part of the batch update set you want to revert.
View the Update Set:
- Open the specific update set to view the list of changes.
Manually Revert Changes:
- For each entry in the update set (like a Business Rule, Script Include, etc.), you need to:
- Navigate to the affected record (such as the Business Rule or Client Script).
- Check the previous version using the Versions related list at the bottom of the form.
- Revert the record to the desired previous version by clicking on the Revert to this version icon.
you have a solid understanding of how to revert an individual update set in ServiceNow! Grouping update sets into batches is indeed a smart way to manage changes and minimize errors.
When reverting changes, it's also a good practice to document what you've reverted for future reference. This can help maintain clarity in your update management process and ensure that all team members are aware of the changes made
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2024 07:27 AM - edited 09-28-2024 07:27 AM
Hi @Ketan Pandey ,
Already @Sandeep Rajput has nicely explained the best approach (batch update) to take. I try to share some information on why Batch is better than Merge as the best approach considering the below limitations of Merge update.
1. In merging of update sets, all updates are merged into a new update set, hence you would not be able to identify later which update set had what all updates developed by individual developers (creators of individual update sets) in case you need to revert updates from any particular update set.
2. In merge, if multiple update sets had the updates (versions) of a same script (BR/CS etc) then the new merged update set will have just the latest version of that script. So the version control is gone, if you want to back track the version details later.
You will overcome the above issues if you go for Batch update, which will create basically a kind of a wrapper update set under which all the child (batched) update sets are kept intact as individual update sets including maintaining the order of child update sets internally.
If this address your question, please mark this response correct by clicking on Accept as Solution and/or Kudos.
You may mark this helpful as well if it helps you.
Thanks,
Animesh Das
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2025 11:16 AM
Hi @Ketan Pandey , Marykayintouch Managing multiple update sets can create challenges, such as committing them in the wrong order or accidentally omitting one or more sets. To prevent these issues, it's helpful to group completed update sets into a batch.
Reverting an Individual Update Set from a Batch in ServiceNow:
Follow these steps to revert an individual update set within a batch:
Identify the Update Set:
- Navigate to System Update Sets > Local Update Sets in the application navigator.
- Search for the update set that was part of the batch you want to revert.
View the Update Set:
- Open the specific update set to see the list of changes made.
Manually Revert Changes:
- For each change in the update set (e.g., Business Rule, Script Include), follow these steps:
- Go to the affected record (such as a Business Rule or Client Script).
- Review the previous version by checking the Versions related list at the bottom of the form.
- Revert the record to the desired version by clicking the Revert to this version icon.
- For each change in the update set (e.g., Business Rule, Script Include), follow these steps: