Sometimes you make customization changes outside an update set context, or discover that a record didn't get captured automatically. This guide shows you two methods to retroactively add customization records to an update set so your changes deploy properly.
Why records miss update sets
Changes made outside an update set context — debugging in production, emergency fixes, or working in Global scope without thinking — don't get captured automatically. Platform admins and developers discover this during deployment when customizations exist in one environment but not another. The bigger problem is that some records can't be captured retroactively at all, which means those changes have to be recreated manually in target environments.
How manual capture works
ServiceNow provides two ways to manually add records: right-clicking the record header for quick single additions, or using the update set record picker for bulk operations. Only customization-layer records can be captured — business rules, UI policies, client scripts, form configurations. You cannot capture data records like incidents or users, and some platform records like scheduled jobs or email accounts resist capture. The system creates an update set record that represents the current state of your customization, not the delta from some previous version.
Building capture into your workflow
Once you understand which records capture cleanly, the next step is preventing missed captures in the first place. Set a default update set for emergency work, use update set switching more deliberately, and audit your customizations periodically to catch strays. For complex deployments, consider using the update set preview feature to validate that all your intended changes are actually included before committing to production moves.
Before you start
- •admin role or sufficient access to modify update sets
- •an existing update set in 'In Progress' state
Sourdough: ServiceNow Monitoring and Analytics
A Chrome extension for ServiceNow Admins and Developers with essential tools, analytics, graphs and monitoring features.
Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.
Step by step
Navigate to the customization record
Open the record you want to add — a business rule, client script, UI policy, or other customization. The record must be a platform customization, not data. You'll see the record's form with its current field values and configuration.
Right-click the record header bar
Right-click anywhere on the blue header bar that shows the record type and number (like 'Business Rule BR0010001'). Select 'Add to Update Set' from the context menu. If this option doesn't appear, the record type cannot be captured this way — skip to step 4 for the alternative method.
Select the target update set
Choose which update set should contain this record from the dropdown. The system shows all update sets in 'In Progress' state that you have access to modify. Click OK to add the record. You'll see a confirmation message and the record is now tracked in that update set.
If your target update set doesn't appear in the list, check that it's still in 'In Progress' state and you have write access to it.
Use record picker for bulk additions
Navigate to System Update Sets > Local Update Sets and open your target update set. In the Customer Updates related list, click 'Add Customer Update'. This opens a record picker that lets you search for and select multiple customization records at once.
Search and select records
Use the filters to find your records by table, name, or other criteria. Select the records you want to include and click 'Add selected'. The system validates each record and adds the capturable ones to your update set. Records that can't be captured will show error messages explaining why.
Verify the additions
Back in your update set, check the Customer Updates related list to confirm your records were added. Each entry shows the table, record name, and operation type. Click into individual update records if you need to see exactly what field values will be deployed.
Best practices
Never manually add data records to update sets — only add customization metadata like business rules, scripts, and form configurations.
Check the Customer Updates list after manual additions to verify the records actually got captured — some record types silently fail to add.
Use the bulk record picker method when you have multiple related records to add, like a business rule and its associated script include.
Set a default update set for your user profile to reduce the chances of making changes outside update set context in the first place.
Review update set contents before deployment using the preview feature — manually added records sometimes capture dependencies you didn't expect.
Test Your Knowledge
Quick 3-question quiz — see how your ServiceNow skills stack up.
A list view on a table with millions of records is slow. Best fix?
Select an answer to continue