Contents Now Platform App Engine Previous Topic Next Topic Merge update sets Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share Merge update sets You can merge multiple update sets into a single update set. This capability is supported for backward compatibility with earlier releases of the ServiceNow® platform. The newer batch update sets feature accomplishes the same outcome with a more predictable and robust solution. Before you begin Note: You cannot "unmerge" update sets once they have been merged. Procedure Navigate to System Update Sets > Merge Update Sets. By default, the list is filtered to only show update sets that are In progress. Alternatively, navigate to System Update Sets > Merge Completed Sets. By default, the list is filtered to only show update sets that are in the Complete state. For example, you may want to use this filter after pushing changes or transferring update set from a development to a test instance. Filter the list to show only the update set that you want to merge. You can only merge update sets that belong to the same application. Figure 1. Merge update sets Enter a Name for the new update set. Updates are moved to this new update set during the merge process. (Optional) Enter a Description for the update set. Click Merge. In the confirmation dialog box, click OK. The new update set is created. The most recent change for each object is moved from the original sets to the new set. Only changes that are not merged into the new set remain in the original sets. A message indicates how many updates were moved and how many were skipped. For example, if both update sets modify the Incident form, only the most recent change is moved to the new update set. The other modification remains in its original update set to provide a record of the changes that were not moved.Note: The system determines which record is the most recent by comparing the Updated field for the records, NOT the sys_updated_on value in the payload. [Recommended] Verify that the correct changes were moved to the new set by scrolling down to the Merged Update Sets related list and opening the old update set records. [Recommended] Delete or empty the original update sets to avoid committing an older change by mistake. The system does not remove updates that were not merged into the new set. DO NOT move updates "left behind" in old sets into the new set. On this page Send Feedback Previous Topic Next Topic
Merge update sets You can merge multiple update sets into a single update set. This capability is supported for backward compatibility with earlier releases of the ServiceNow® platform. The newer batch update sets feature accomplishes the same outcome with a more predictable and robust solution. Before you begin Note: You cannot "unmerge" update sets once they have been merged. Procedure Navigate to System Update Sets > Merge Update Sets. By default, the list is filtered to only show update sets that are In progress. Alternatively, navigate to System Update Sets > Merge Completed Sets. By default, the list is filtered to only show update sets that are in the Complete state. For example, you may want to use this filter after pushing changes or transferring update set from a development to a test instance. Filter the list to show only the update set that you want to merge. You can only merge update sets that belong to the same application. Figure 1. Merge update sets Enter a Name for the new update set. Updates are moved to this new update set during the merge process. (Optional) Enter a Description for the update set. Click Merge. In the confirmation dialog box, click OK. The new update set is created. The most recent change for each object is moved from the original sets to the new set. Only changes that are not merged into the new set remain in the original sets. A message indicates how many updates were moved and how many were skipped. For example, if both update sets modify the Incident form, only the most recent change is moved to the new update set. The other modification remains in its original update set to provide a record of the changes that were not moved.Note: The system determines which record is the most recent by comparing the Updated field for the records, NOT the sys_updated_on value in the payload. [Recommended] Verify that the correct changes were moved to the new set by scrolling down to the Merged Update Sets related list and opening the old update set records. [Recommended] Delete or empty the original update sets to avoid committing an older change by mistake. The system does not remove updates that were not merged into the new set. DO NOT move updates "left behind" in old sets into the new set.
Merge update sets You can merge multiple update sets into a single update set. This capability is supported for backward compatibility with earlier releases of the ServiceNow® platform. The newer batch update sets feature accomplishes the same outcome with a more predictable and robust solution. Before you begin Note: You cannot "unmerge" update sets once they have been merged. Procedure Navigate to System Update Sets > Merge Update Sets. By default, the list is filtered to only show update sets that are In progress. Alternatively, navigate to System Update Sets > Merge Completed Sets. By default, the list is filtered to only show update sets that are in the Complete state. For example, you may want to use this filter after pushing changes or transferring update set from a development to a test instance. Filter the list to show only the update set that you want to merge. You can only merge update sets that belong to the same application. Figure 1. Merge update sets Enter a Name for the new update set. Updates are moved to this new update set during the merge process. (Optional) Enter a Description for the update set. Click Merge. In the confirmation dialog box, click OK. The new update set is created. The most recent change for each object is moved from the original sets to the new set. Only changes that are not merged into the new set remain in the original sets. A message indicates how many updates were moved and how many were skipped. For example, if both update sets modify the Incident form, only the most recent change is moved to the new update set. The other modification remains in its original update set to provide a record of the changes that were not moved.Note: The system determines which record is the most recent by comparing the Updated field for the records, NOT the sys_updated_on value in the payload. [Recommended] Verify that the correct changes were moved to the new set by scrolling down to the Merged Update Sets related list and opening the old update set records. [Recommended] Delete or empty the original update sets to avoid committing an older change by mistake. The system does not remove updates that were not merged into the new set. DO NOT move updates "left behind" in old sets into the new set.
