Upgrade skipped customization: local change preserved over base system update

A base system record (like UI Policy, Business Rule, or Script Include) was customized locally and conflicts with incoming upgrade changes to the same record. (high likelihood)

Out-of-box form layouts, list layouts, or views were modified and now conflict with updated versions in the upgrade package. (high likelihood)

Base system ACLs, roles, or security configurations were customized and conflict with security updates in the new release. (medium likelihood)

Core application files or system properties were modified directly instead of being extended or overridden through proper customization methods. (medium likelihood)

Third-party applications or store apps modified base system records that are now being updated by the platform upgrade. (low likelihood)

Step 1: Navigate to System Diagnostics > Upgrade History and review the detailed upgrade log to identify which specific records were skipped during the upgrade.

Step 2: Go to System Definition > Dictionary Override or System Definition > Tables and identify customized base system records by filtering for records with 'sys_package' field not equal to 'global' or 'NULL'.

Step 3: For each skipped record, compare your customized version with the updated base system version using System Definition > Compare Records or by checking the record's version history.

Step 4: Determine if your customizations are still needed by reviewing business requirements and checking if the new base system functionality addresses your original customization needs.

Step 5: If customizations are still required, merge the changes manually by incorporating necessary custom logic into the updated base system record while preserving new platform functionality.

Step 6: If customizations are no longer needed, revert to the base system version by deleting the customized record or using System Definition > Revert to Base System.

Step 7: Test the affected functionality thoroughly in a development or testing environment before applying changes to production.

Step 8: Document the resolution decisions and update your customization inventory to track which base system records have been modified.