Is It Possible to Move Only a Specific Configuration Change Using Update Sets?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
Hi Community,
I have a question regarding Update Sets in ServiceNow.
Suppose I make 3–4 configuration changes to the same form or within the same application. However, I want to move only one specific configuration change to the Production instance using an Update Set.
The issue I am facing is that when I add the configuration to an Update Set, ServiceNow captures the entire related form or application configuration, including my previous changes.
As a result, when I move the Update Set to Production, all the previously made changes are also included in the deployment.
My question is:
Is there any way to selectively capture only one specific configuration change while excluding the other changes made to the same form or application?
For example, if I make four changes to a form but want to deploy only one of them, can I achieve this without moving the remaining three changes?
Is there any recommended approach or best practice to handle this scenario?
Any suggestions or guidance would be greatly appreciated.
Thanks in advance!
#ServiceNow Platform, #PlotformCapabilities
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hi @RaveendraK,
yes, but not by trimming the Update Set after the fact. The core issue is how ServiceNow tracks changes.
Update Sets capture records, not individual edits. A form layout, a UI policy, or a client script is stored as a single record (for example sys_ui_section for a form section). Every time you save it, the Update Set stores a new version of the whole record. So if you changed the same form four times, the Update Set holds the entire current state of that record, and deploying it carries all four changes. There is no field-level or “diff-only” capture.
Recommended approach:
- Use a separate Update Set per change (best practice). Before you start each change, create a new Update Set and set it as current. One logical change, one Update Set. This is the standard guidance and avoids the problem entirely.
- Keep related changes on different records where possible. For example, put logic in a separate UI Policy or Client Script rather than editing one big script, so each change is its own record and can be moved independently.
- If the changes are already mixed (the situation you’re in):
- Open the Update Set and check the Customer Updates related list. Entries are per record, so if the changes live on different records, you can remove or move the unwanted entries.
- Use Move to another update set on the entries you don’t want to ship, then deploy only what remains.
- If all four changes are on the same record, you can’t split them. Instead, revert the record in your dev instance to the version you want to ship (via Versions / Compare to Current, then Revert to this version), commit that to a clean Update Set, then re-apply the other changes in a different Update Set afterward.
- Alternatively, apply only the one change you want manually on a clean basis in the target instance.
- Watch for skipped or out-of-order changes. Moving entries between sets can create dependency problems (for example, a later change referencing something in the set you held back). Use the preview step on the target instance to catch missing dependencies and collisions before committing.
- For larger teams, consider Application Scope + Source Control (Git) or Deployment tooling. Scoped apps with source control let you commit and promote at a finer granularity, with branches for in-progress work, which handles parallel changes much better than update sets alone.
Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards,
Tarun