Understanding the Issue

The issue arises when reviewing the mappings of the Contact data stream, where the Id field is mapped to multiple fields on the Account Contact DMO, including Phone, Email, and Address. When attempting to delete these mappings, an error occurs, indicating that these mappings come automatically from installing the Sales Data Kit.

These mappings are a result of the relationship between DMOs, where the Contact Id is used as the Individual Id and Contact Point Email Party field, allowing for the retrieval of all email addresses related to a given Individual. However, the inconsistent naming of standard fields in standard objects by the Salesforce team leads to confusion in the mapping UI.

The root cause of this issue is the inconsistent naming of standard fields in standard objects by the Salesforce team, leading to confusion in the mapping UI. The fields are actually meant to have Id in the end, such as Account Contact.Contact Point Email Id, which would make the default mapping logical.

Resolving the Issue

To resolve this issue, it is essential to understand the relationships between DMOs and the intended use of the mappings. The joining fields must have specific values, which is what mapping is for, defining how records will be created in each DMO and ensuring relationships work as intended.

By understanding the relationships between DMOs and the intended use of the mappings, teams can resolve the issue and ensure that their data is accurately mapped and related.

example_mapping.json

{
  "mappings": [
    {
      "source": "Contact.Id",
      "target": "AccountContact.ContactPointEmailId"
    }
  ]
}

Heads up: When working with Data 360, it is crucial to understand the relationships between DMOs and the intended use of the mappings to ensure accurate data mapping and relationships.

Best Practices

Checklist for Resolving Mapping Issues in Data 360

• Understand the relationships between DMOs and the intended use of the mappings
• Review the mappings of the Contact data stream to the Account Contact DMO
• Check for inconsistent naming of standard fields in standard objects
• Verify that the joining fields have specific values
• Use the Relationships tab to understand the relationships between DMOs
• Document the mappings and relationships for future reference
• Test the mappings and relationships to ensure accuracy

What is the difference between mapping and relationship in Data 360?

The difference between mapping and relationship in Data 360 is that mapping defines how records will be created in each DMO, while relationship defines the connections between DMOs.

Why are the mappings visible in the mapping UI?

The mappings are visible in the mapping UI because they define how records will be created in each DMO, ensuring relationships work as intended.

How can I resolve the issue with the Id field being mapped to multiple fields?

To resolve the issue, understand the relationships between DMOs and the intended use of the mappings, and review the mappings of the Contact data stream to the Account Contact DMO.

What is the purpose of the Relationships tab in Data 360?

The Relationships tab in Data 360 is used to understand the relationships between DMOs, and to verify that the joining fields have specific values.

How can I ensure accurate data mapping and relationships in Data 360?

To ensure accurate data mapping and relationships in Data 360, understand the relationships between DMOs, review the mappings, and verify that the joining fields have specific values.