Salesforce has introduced a new restriction to prevent mapping to a Standard DMO when a Custom DMO with the same name exists (e.g., ssot_Account__dlm and Account__dlm). This change is designed to prevent conflicts between custom and standard DMOs that could lead to errors during the mapping process.
If an organization already has a Custom DMO with the same name as a Standard DMO, mapping to the Standard DMO will be restricted. However, customers will still be able to map to the Custom DMO. This restriction helps ensure clarity and consistency by avoiding conflicts between the standard and custom versions of the same object.
Customers who already have mappings using a Custom DMO can continue to edit these mappings through the mappings screen. The restriction applies specifically to Standard DMO mappings when a Custom DMO with the same name exists.
Salesforce prevents the creation of a Custom DMO with the same API name as a Standard DMO. While the label of the DMO (e.g., “Account”) can be the same, the API name (developer name) must differ.
003964473

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.