To prevent customizations from being overwritten by system upgrades, the upgrade process automatically skips changes to objects that have been customized. You may want to overwrite your customizations when a software upgrade
contains a feature that you would like to implement.
Before you begin
Role required: admin
About this task
To identify customized objects, the system adds a corresponding record in the Customer Updates [sys_update_xml] table. The table maintains the current version information for all objects that have been
customized. The upgrade process skips changes to objects that have entries in the table. The upgrade process does not skip objects if only excluded fields have changed.
Procedure
-
Navigate to Upgrade History using one of the following ways.
| Option |
Navigation |
| Using left navigation |
Navigate to . |
| Using Admin tab option |
Navigate to . |
A list of upgrades is displayed.
-
Select the desired software version.
-
Filter the Upgrade Details related list by Disposition is Skipped.
- Optional:
Add another filter condition for Changed is True to return only the objects that have changed since the last upgrade.
-
Select the update record to implement.
The File differences field displays a side-by-side comparison of the customization and the default version. Deletions are highlighted in red, additions in green, and modifications in
yellow.
-
Click Revert to base system to overwrite your customized object with the system default version.
- The Disposition changes from Skipped to Reverted.
- After you revert a customization, you have the option to click Reapply Changes to reapply your customizations (undo the revert).