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

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Update set batching

# Update set batching {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read

Batch update sets enable you to group update sets together so you can preview and
commit them in bulk.{#us-hier-overview__e5v_1qk_yy}

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.  
Note:  
To preserve the update set batch hierarchy while cloning, set only the parent update set to 'Ignore' status and leave all other update sets as 'Complete'. This will prevent batch sets from cloning and preserves the batch update set hierarchy.
The system organizes update set batches into a hierarchy. One update set can act as the parent for multiple child update sets. A given set can be both a child and parent, enabling multiple-level hierarchies. One update set at the top level of the hierarchy acts as the base update set.  
When you preview or commit the base update set, you preview or commit the entire batch. The system determines the processing order, and checks for collisions, based on the dates the changes were recorded, and on their sequential ancestry. Their ancestries are the specific instances in which the changes in the update sets took place.  
Note:  
For more details, see [Compare local update sets](https://www.servicenow.com/docs/jlVGDMiJy2DNMkmlWg9VnA#t_CompareLocalUpdateSets "Administrators can preview local and remote (retrieved) update sets and compare the sets with one another to resolve conflicting changes.") and [View customizations and compare with current version](https://www.servicenow.com/docs/mFehRaKLWP~~W3~zm~FGwA "View the customizations that make up an update set and compare the update to the current version.").

## Example of batched update sets {#us-hier-overview__section_f52_psx_41b}

The list of update set records reflects the batch hierarchy in the Parent andBatch Base columns. Figure 1. List of batched update sets   

Figure 2. Diagram of batched update set hierarchy   

## Create a batch update set {#ariaid-title2}

You include an update set in a batch by specifying another update set as its parent.{#us-hier-create__tqk_3qk_yy}

### Before you begin

Role required: admin

Adding a WIP update set to a completed batch resets the batch base to WIP.{#us-hier-create__db3_jqk_yy}

### Procedure

1. Navigate to AllSystem Update SetsLocal Update Sets.
2. Select the record for an update set that you want to include as a child in the batch. {#us-hier-create__ndv_jqk_yy}
3. On the Update Set record, navigate to the Parent field and select the update set to act as the parent. {#us-hier-create__hcl_z4d_py}
4. Click Update.  
   The system returns to the list of Update Sets. If the Parent column is visible, it shows the parent for the newly-created child. {#us-hier-create__bvl_bpd_py}

## Retrieve batched update sets {#ariaid-title3}

You retrieve a batch of update sets using the same process you would as for any
individual update set.

### Before you begin

Role required: admin

### Procedure

To retrieve a batch of update sets, follow the same process for the batch base as you would for any individual update set.  
The system will process the entire batch at once. For details, see [Retrieve an update set](https://www.servicenow.com/docs/Rvpxsh5KqE8P6ui5ERTfKA "Retrieve completed update sets from another instance.").

## Preview a batch of update sets {#ariaid-title4}

You can preview at once all the update sets belonging to a batch.{#us-hier-preview__u5j_rqk_yy}

### Before you begin

Role required: admin

You must have retrieved the update sets from the source
instance.

### Procedure

1. Navigate to AllSystem Update SetsRetrieved Update Sets {#us-hier-preview__uvz_brd_py}
2. From the list of retrieved update sets, select the batch base for the batch you want to preview.  
   You cannot separately preview an update set that is a child in a batch. You must preview the entire batch by previewing the batch base. If necessary, you can [remove the child update set](https://www.servicenow.com/docs/c~3WJkDBQDudWvveF9e07Q#us-hier-reorg "You can remove an individual update set from the batch or change its parent.") from the batch by editing its record's parent field. {#us-hier-preview__ijc_sqk_yy}
3. Click Preview Update Set Batch. {#us-hier-preview__ajw_2rd_py}
4. If the system found problems, preview the problems.
   1. Click the Preview Problems for Batch and [resolve the problems](https://www.servicenow.com/docs/c9mHUfewQARmLN5rI510EA#t_AddressAnUpdateSetPreviewProblem "Preview an update set to detect and resolve problems that may occur if you commit the updates on the local instance.") as you normally would for any update set. {#us-hier-preview__kpz_rrd_py}
   2. When you have resolved all the problems, click Run Preview Again for Batch. {#us-hier-preview__hnb_xrd_py}
   {#us-hier-preview__substeps_jzv_ygk_kyb} {#us-hier-preview__pc3_prd_py}

## Commit a batch of update sets {#ariaid-title5}

You can commit at once all the update sets belonging to a batch.

### Before you begin

Role required: admin

Before committing, you must have previewed the update sets
from the source instance and resolved any collisions.

### Procedure

1. Navigate to AllSystem Update SetsRetrieved Update Sets {#us-hier-commit__uvz_brd_py}
2. From the list of retrieved update sets, select the batch base for the batch you want to preview.  
   You cannot separately commit an update set that is a child in a batch. You must commit the entire batch by committing the batch base. If necessary, you can remove the child update set from the batch by editing its record's parent field. {#us-hier-commit__vvz_brd_py}
3. Click Commit All Update Sets. {#us-hier-commit__hnb_xrd_py}

## Reorganize a batch of update sets {#ariaid-title6}

You can remove an individual update set from the batch or change its
parent.

### Before you begin

Role required: admin

### Procedure

1. Navigate to AllSystem Update SetsLocal Update Sets. {#us-hier-reorg__oys_nvb_ty}
2. Select the record for an update set that you want to move or remove as a child in the batch. {#us-hier-reorg__tc5_54d_py}
3. On the update set record, navigate to the Parent field and select the new update set to act as the parent. {#us-hier-reorg__hcl_z4d_py}
4. To remove the update set from the batch, delete any text from the Parent field and leave it blank. {#us-hier-reorg__mbk_5wb_ty}
5. Click Update.  
   The system returns to the list of update sets. If the Batch Base column is visible, it shows the parent for the newly-created child. {#us-hier-reorg__bvl_bpd_py}
{#us-hier-reorg__kys_nvb_ty}

### What to do next

If the system property glide.update_set.auto_preview is set to true, the system automatically starts the preview process after the record is updated with a new parent. If this property is false, you must start the process manually. For more information on the preview process, see [Preview a batch of update sets](https://www.servicenow.com/docs/c~3WJkDBQDudWvveF9e07Q#us-hier-preview "You can preview at once all the update sets belonging to a batch.") .

## Back out batched update set {#ariaid-title7}

Back out a batched update set by following the backout procedure for the base update
set for the batch. You can also back out any child update set independently.
The following rules apply when backing out an update set that belongs to a batch:
* If the update set has a parent value, the system clears the parent value and treats the update set as an independent update set, or as a new batch base if it has any children.
* The system backs out the selected update set, plus any children of the backed-out update set.

{#us-batch-backout__ul_iyr_fxb_h1b}To learn more, see [Back
out an update set](https://www.servicenow.com/docs/qDyNx3WJL8mobweUt8lHPQ "You can back out changes to existing records for any committed update set.") and [Update set
batching](https://www.servicenow.com/docs/c~3WJkDBQDudWvveF9e07Q#us-hier-overview "Batch update sets enable you to group update sets together so you can preview and commit them in bulk.")

### Example of backing out a batched update set {#us-batch-backout__section_pmd_xqx_41b}

If you back out Update Set 1.1 from the batch shown in [List of batched update sets before backing out an update set](https://www.servicenow.com/docs/c~3WJkDBQDudWvveF9e07Q#us-batch-backout__fig_g3f_syx_41b), the result is the batch shown in
[List of batched update sets after backing out Update Set 1.1](https://www.servicenow.com/docs/c~3WJkDBQDudWvveF9e07Q#us-batch-backout__fig_px1_xyx_41b).
Figure 3. List of batched update sets before backing out an update set   

Figure 4. List of batched update sets after backing out Update Set 1.1   

[Hierarchical diagram of Update Set batch](https://www.servicenow.com/docs/c~3WJkDBQDudWvveF9e07Q#us-batch-backout__fig_xcs_fyd_p1b) shows the hierarchy both
before and after the back out. The red boxes show the update sets the system backs out if
you back out Update Set 1.1.
Figure 5. Hierarchical diagram of Update Set batch   

*[\>]: and then