A skipped manual merge is an upgrade record left unchanged because updating it needs a person to reconcile your customized version with the incoming change. To clear one, open it from the skipped list, use Resolve Conflicts to bring across the fields you want, and click Merge. Retaining your version or reverting to base are the alternatives.
What a skipped manual merge record is
An upgrade replaces base system records with newer versions. When you have customized one of those records, the upgrade does not overwrite your work. It skips the update and keeps a record of the conflict, so your customization stays in place until someone decides how the two versions should be reconciled.
Customization is the common reason a record gets skipped. For the wider concept, see customization versus configuration. The manual merge case is the one the upgrade cannot settle by itself. In the Disposition field, Skipped Manual Merge means the system did not change the record because updating it requires manual intervention. Before the upgrade runs, the same situation appears in the upgrade preview as Predicted Skip (Manual Merge).
Each skipped record also carries a priority from one to five. Working from priority 1 downward puts the UI-facing records first in your queue.
Finding skipped records after an upgrade
Start in the Upgrade Monitor. In the Australia release, go to All > Upgrade Center > Upgrade Monitor. While an upgrade runs, the Upgrade Progress screen shows each stage. When it finishes, the Upgrade Summary Report replaces it. For the release names used in these steps, see ServiceNow release versions explained.
The Skipped Records section of that report gives three counts: the total skipped, the number still to review, and the number already reviewed. It also sorts skipped records by priority, by product, and by whether the code in the record changed. Click the Review changes link in the Skipped box to open the System Upgrades form, then scroll to the Review Skipped Records section to reach the Skipped Changes to Review related list.
The same list is reachable from upgrade history. In the Australia release, go to All > Upgrade Center > Upgrade History, select the software version, and open the related list. An upgrade history record is created for each upgrade that runs, and the visual task board view shows the resolution status of the skipped records in the current upgrade. The Xanadu release uses the same route, All > Upgrade Center > Upgrade History.
Both routes require the admin role.
Working through one skipped record
Open a record from the Skipped Changes to Review list and the Upgrade Details form appears. It shows the file name, the priority, a comment box, the resolution, the disposition, the record type, the target name, the plugin and the table.
Review the differences before you decide. For a text field, click inside the field to open the Diff/Merge tool, then click a text box to see the detailed differences.
Add a comment when the reason for the decision should be visible later. Future reviewers can then see what you did and why. Choose one action, click Update, and repeat for the next record.
Customized objects that did not change in the base system since the last upgrade need no action from you. The Customization Unchanged related list shows those records. To narrow the work, filter the Upgrade Details related list by Disposition is Skipped, then add the Changed by vendor field to return objects the vendor changed since the last upgrade.
Choosing between merge, retain, revert and defer
Each action sets a different disposition or resolution status on the record. The table lists the options in the Australia release.
| Choice | What you do on the record | Result |
|---|---|---|
| Retain | Review the changes, then set Resolution Status to Reviewed and Retained | Your customized record stays as it is and is not updated. It moves to Skipped Changes Reviewed. |
| Merge | Click Resolve Conflicts, click the right-arrow button for each field to bring across, then click Merge | Resolution Status changes to Reviewed and Merged. It moves to Skipped Changes Reviewed. |
| Revert | After reviewing the changes, click Revert to Base System | Disposition changes to Reverted and the status to Reviewed and Reverted. The system creates a Customer Update record. |
| Review, no action | Set Resolution Status to Reviewed | The record is not changed. It moves to Skipped Changes Reviewed. |
| Defer | Choose Not Reviewed in the Resolution list and click Update | The record stays on Skipped Changes to Review. |
Merging is usually the most hands-on option, because you choose the final content field by field. On the Resolve Conflicts form, use the right-arrow button for each field you want to bring across, edit the detailed differences in the text box where needed, then click Merge.
Revert suits the case where the upgrade brings a feature you want and your customization should give way. It overwrites your customized object with the default version. It can be undone: Reapply Changes restores your customization at any time after the revert.
Retain suits the case where your customization should stay exactly as it is. Defer suits a decision you are not ready to make, and a record left at Not Reviewed stays on the list until you return to it.
Reviewing manual merge skips before the upgrade runs
The Upgrade Preview shows predicted results before an upgrade runs. In the Australia release, go to All > Upgrade Center > Preview module. Select the target version, then click Go or Refresh Preview. When it is complete, click View preview details on the Previewing version card.
The preview’s related lists show each predicted record with its predicted disposition, priority and resolution. The Total record changes figure includes records predicted to be skipped.
Each predicted record carries one of six dispositions: Predicted Insert, Predicted Update, Reverted, Predicted Skip, Predicted Skip (Manual Merge) and Predicted Skip (Apply Once). A Predicted Skip (Manual Merge) line means the system will not change that record because updating it needs manual intervention, so it is the line to plan for before the upgrade runs. A Reverted line marks a record returned to its base version that will not be skipped on the next upgrade.
Predicted customization skips can be addressed before the upgrade runs, which can stop the skip from happening. The preview’s Resolution column lists the ways to resolve a conflict: Not reviewed, Reviewed, Review not needed, Reviewed and Retained, and Reviewed and Reverted.
Priority and claim status
In the Australia release, priority 1 covers UI pages, UI macros and similar records. Priority 2 covers business rules and security ACLs. Priority 3 covers reports. Priority 4 covers form sections and choice sets. Priority 5 covers everything else.
The Claim Status field records whether competing applications claimed the same file. N/A means there is no claim. Won conflict means the file loaded but clashes with one loaded before it, so confirm the outcome you intended. No conflict means no clash, though the result is still worth checking. Lost conflict means another application had the stronger claim, so decide which version should load, or whether they should be merged.
Carrying review decisions to another instance
The system tracks changes in an update set, so you can apply them to another instance later. Upgrade details records do not move between instances, though. They belong to one upgrade on one instance. To keep the comments and resolutions, export the skipped list from the instance before you move on. For how update sets compare with the application repository, see update sets versus the application repository.
Review in the item’s own application scope, or the update set can pick up items from other scopes. After the upgrade, test each change you made to the records on the skipped list, because a merge or revert changes working configuration just as the upgrade does. For a broader checklist, see the upgrade testing and acceptance checklist.
Frequently asked questions
What is the difference between retaining and merging a skipped record?
Retaining keeps your version as it is and sets the resolution to Reviewed and Retained. Merging opens the Resolve Conflicts form, where you choose each field to bring across from the base system, and then sets the resolution to Reviewed and Merged.
Where do records I have not decided on yet appear?
They stay on the Skipped Changes to Review list. Choosing Not Reviewed keeps a record there until you return to it.
Can I undo a revert?
Yes. Reapply Changes restores your customization at any time after the revert.
Can I see manual merge skips before the upgrade runs?
Yes. The Upgrade Preview shows Predicted Skip (Manual Merge) for records that need hands-on review, so you can plan that work in advance.
Do my review comments move to a new instance automatically?
No. Upgrade details records do not migrate between instances, so export the skipped list from the current instance to keep the comments and resolutions.