Loading

Data Cloud: Restrictions on Mapping Standard DMO When Custom DMO Exists with Same API Name

Udgivelsesdato: Aug 25, 2025
Beskrivelse

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.

Løsning

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.

  • If a Custom DMO exists with a conflicting API name, customers will be allowed to map to the Custom DMO but not to the Standard DMO.
  • If customers would like to map to the Standard DMO, they will need to either:
    • Delete the Custom DMO that has the conflicting name, or
    • Remap the Custom DMO sources to a new DMO that does not have a name conflict with the Standard DMO, and then delete the original Custom DMO.
Vidensartikelnummer

003964473

 
Indlæser
Salesforce Help | Article