---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/application-development

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Working with update sets

# Working with update sets {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Manage your
customizations and resolve potential collisions before you move them to another instance.
To create an update set see [Create and select an update set as the current set](https://www.servicenow.com/docs/V2FPipBbxKjHH1GzrXLRwQ "Create an update set to store customization changes and select it as the current set.").

When the update set is completed, you can transfer the update set to another instance according to your test process. See [Update set transfers](https://www.servicenow.com/docs/zs2pnv12U5qWHn3B4nLcJQ "When an update set is completed, you can transfer it between instances to move customizations from development, through testing, and into production.").  
If a customization is made in the wrong update set

1. Switch to the desired update set.
2. Modify the object (record) that was originally changed. You can make a trivial change, such as adding a field.
3. Save the record.
4. Back out the change just performed, and then save the record again. This action ensures that the latest version of the object is included in the desired update set and prevents duplicate updates for the same
   object in a single update set.

{#using-system-update-sets__ol_x2b_f2y_4y}Don't change the Update Set field value in a Customer Update record.
* **[Create and select an update set as the current set](https://www.servicenow.com/docs/V2FPipBbxKjHH1GzrXLRwQ)**   
  Create an update set to store customization changes and select it as the current set.
* **[Select the current update set in Unified Navigation](https://www.servicenow.com/docs/28YcuB7y6rS0GQ2gspP_Bw)**   
  You can change the current update set at any time using the update set picker in Unified Navigation.
* **[View customizations and compare with current version](https://www.servicenow.com/docs/1xq7L1_6IkQrCLTOKy1fEQ)**   
  View the customizations that make up an update set and compare the update to the current version.
* **[Navigation between records](https://www.servicenow.com/docs/aMQ0wFyI~K5xXTLI1uzXNw)**   
  Navigate between a customer update record and the customized object or the application file for the object.
* **[Compare local update sets](https://www.servicenow.com/docs/49URwz6ZmN64VeizSVZG9Q)**   
  Administrators can preview local and remote (retrieved) update sets and compare the sets with one another to resolve conflicting changes.
* **[Preview a remote update set](https://www.servicenow.com/docs/0kuMPeoACZH_aizb3hJfnw#t_PreviewARemoteUpdateSet)**   
  Previewing checks a retrieved update set against the local instance to find issues. Resolve all problems before committing the update set.
* **[Commit an update set](https://www.servicenow.com/docs/pWyuhY_Pxe5zjH9S9e9XWw)**   
  After resolving any issues from previewing, commit the update set to apply all changes and generate a local copy with records of each update.
* **[Retrieve an update set](https://www.servicenow.com/docs/lZVwwd_oLLPyA5cFpoYtmQ)**   
  Retrieve completed update sets from another instance.
* **[Back out an update set](https://www.servicenow.com/docs/uxAu8tk_VDIpKe7wRwyEXQ)**   
  You can back out changes to existing records for any committed update set.
* **[Mark an update set complete](https://www.servicenow.com/docs/LJijlJEA~BUTlMp2L0Hehw)**   
  When you have completed the customizations and compared local update sets to resolve conflicts, mark the update set as Complete.