Resolve a skipped update and set a resolution status
- UpdatedJul 31, 2025
- 3 minutes to read
- Zurich
- Upgrade Center
Review the reason for each skipped record to resolve each skipped update after an upgrade.
Before you begin
About this task
You resolve an update by either retaining the customization or by merging or overwriting the customization with the base system update.
Note: Objects that are customized and that did not change in the base system since the last
upgrade require no action on your part.
When an object is customized, the system adds a corresponding record to the Customer Updates [sys_update_xml] table and then maintains current version information for all customized objects. The upgrade process skips changes to
objects that have a current version in the Customer Updates table. When you follow the procedure, you perform one of the following actions:
- Retain a customization with no changes
- Retain a customization by merging changes from the updated object
- Revert a customized object to the updated version (that is, overwrite the customization)
- Review the skip and perform no action on the object
Note: If you want to capture your changes in update sets other than the default, ensure that you are in the Application Scope context of the item that you change while reviewing it as part of skipped items. If you are in a
different scope, you may end up with items for different scopes in your update set.
Procedure
Result
Only skipped updates with a Resolution Status of Not Reviewed or without a resolution set appear in the Skipped Changes to Review related list. Any action you take that changes the Resolution Status to a value other than Not Reviewed or --None-- removes the skipped update from list and moves it to the Skipped Changes Reviewed related list.