You are here:
Behavior of Field Maps and Object Maps Maintenance in Winter '23 Release and Beyond
Previously, installing or upgrading the CME package required manual maintenance of field and object maps after the process. This involved running specific jobs that could potentially erase customizations.
After install or upgrade, as part of post-installation steps, you had to manually run these jobs from the CMT Admin Console:
- Field Maps Maintenance - Removes existing CustomFieldMap__c objects and restores the default mappings
- Object Maps Maintenance - Removes existing CustomObjectMap__c objects and restores the default mappings.
Starting with Winter '23 release, automated Push Upgrade steps handle field and object maps during installation and upgrades. This eliminates the need for manual maintenance, reducing the risk of data loss. Remember that,
- If you've deleted any pre-built mapping before package upgrade, then the push Upgrade steps automatically recreates the mapping during package upgrade (given the mapping is still present in the upgrade package).
- If the default pre-built mapping changes in the upgrade package, the Push Upgrade step ignores the mapping in the upgrade package, as it conflicts with an existing mapping on the org.
- You can't opt out of these automated push upgrade steps for field maps and object maps.
- Manual maintenance jobs in the CMT Admin Console still have the same behavior of deleting
existing mappings. Use caution when running them
Note If you are manually removing the pre-configured mappings after each Push upgrade, then modify the source field within the pre-configured mapping itself, instead of deleting it entirely. This change prevents the Push Upgrade from recreating the unwanted mapping. If you've customized the XLI/ServiceDate field, update the source field in the related pre-configured mapping to reflect this change, ensuring your custom settings are preserved after upgrades.
Did this article solve your issue?
Let us know so we can improve!
