Skipped Changes to Review related list To prevent your customizations from being overwritten during system upgrades, the upgrade process skips (does not apply the update to) objects that have been customized. To assist you in tracking and resolving skipped update records that need review, Skipped Changes to Review lists all updates skipped during the upgrade process. By default, the list is filtered by disposition skipped error or (disposition skipped manual merge and changed is true) or (disposition skipped and changed is true) or (disposition skipped(second pass) and changed is true), and the resolution status is either empty or not reviewed. Navigate to System Diagnostics > Upgrade History to view the Skipped Changes to Review related list. Table 1. Skipped Changes to Review related list Field Input Value File name Name of skipped Upgrade Detail record. Disposition Action performed on this file during the selected upgrade: Inserted: The system inserted a new record. Updated: The system updated this record. Deleted: The system deleted this record. Skipped: The system did not change this record in order to preserve customizations. Reverted: This record was reverted to the base version. Table not found: The system could not find the table that contains this record. Unchanged: The system did not change this record because the baseline component has not changed since the last release. Skipped Manual Merge: The system did not change this record because updating it requires manual intervention. Skipped Apply Once: The system skipped this record because it had already applied an update from an xml file in the apply once folder. Not Latest: The system applied a change, but this change was overwritten later during the same upgrade. Priority Relative importance of the conflict that caused the skip based on the following criteria: 1 (highest priority): xml content 2: script or script_plain 3: html content 4: sys_ui_form_section, sys_ui_related_list, or sys_choice_set 5 (lowest priority): other Resolution Reviewed Retained Reverted Comment During the process of resolving a skipped update, you have the option to add a Comment to any record. For example, the comment might explain the action that you took to future reviewers. Target name Name of the record corresponding to the current file. Plugin Plugin that contains the record. Type Current file type (such as Business Rule or UI Policy). Table Table that contains the record. Resolve a skipped update and set a resolution statusTo prevent your customizations from being overwritten during system upgrades, the upgrade process skips (does not apply the update to) objects that have been customized. One of your responsibilities as the administrator is to resolve each skipped update after an upgrade.