Select An Org
Object mappings in the existing DataMappers are removed after the Summer 25 upgrade
Publish Date: Jun 17, 2025
Description
Following the Summer '25 upgrade, we’ve observed that object mappings are being removed from existing DataMappers in instances where the Managed Package Designer is disabled.
This occurs when the fakemapping records, which are automatically generated in the backend are deleted.
Please find sample steps to reproduce -
-
-
Use an existing DataMapper with a linked object mapping as below in a 254 org
- Delete the FakeMappings in the backend
- Deploy the above DataMapper into a 256 environment where Managed Package Designer are disabled.
- Observe that the account object mapping is removed after deployment.
-
Resolution
This is an expected behaviour because:
- When we create DM load and associate an object, system will create `Id` fakemapping records which will be used by core designer for object mapping association.
- The mappings are required ones for core designer, if these mappings are explicitly deleted/cleaned, it leads to the mapping issue.
- The recommendation is to NOT clear the fake mappings as they are being used at the backend.
- To identify the fake mappings, query OmniDataTransformItem entity and filter the records with MigrationValue = 'FAKEMAPPING' to check whether each associated load object has the fake mapping record with OutputFieldName = 'Id' to find the missing ones.
Knowledge Article Number
005036598
Did this article solve your issue?
Let us know so we can improve!
