Microsoft Dynamics 365 Customer Experience Analyst : Configure relationship mappings on Sales tables

In Dynamics 365 Sales, relationship mappings on Sales tables define how data flows between related records, ensuring consistency and reducing manual data entry. For example, when creating a Contact from an Account, relationship mappings automatically copy key fields such as address, phone number, or account details into the new record. These mappings are configured within 1:N or N:1 relationships between tables and allow administrators to decide which fields from the parent record should pre-populate in the child record. This helps maintain data integrity, speeds up record creation, and ensures users have consistent and accurate information across Accounts, Contacts, Opportunities, and other related Sales entities.

What Are Relationship Mappings?

Relationship mappings define how data from a parent table (e.g., Account) is automatically carried over to a related table (e.g., Contact, Opportunity) when a new record is created.

Example: When creating a Contact from an Account, the address, phone, and company name can be auto-filled.

This ensures consistency, reduces manual data entry, and improves data integrity.

Steps to Configure Relationship Mappings in Dynamics 365 Sales

1. Go to Power Apps Maker Portal

• Navigate to https://make.powerapps.com
• Select your Sales environment.

2. Open the Sales Table

• From the left navigation, select Dataverse → Tables.
• Find and select the Sales table (e.g., Account, Contact, Opportunity).

3. Select the Relationship

• Go to the Relationships tab.
• Choose the relationship type:
• 1:N (One-to-Many) → Parent record to child record (Account → Contact).
• N:1 (Many-to-One) → Child record to parent record (Opportunity → Account).
• Pick the relationship you want to configure mappings for.

4. Edit Relationship Mappings

• Open the relationship details.
• Under the Mappings section, add or modify field mappings.

Example: Map Account.Address1 → Contact.Address1

Example: Map Account.Phone → Contact.Phone

5. Save & Publish

• Save the changes.
• Publish customizations so the mappings take effect in Sales forms.

Example Use Case in Sales Tables

When creating a new Opportunity from an Account, the following mappings can be configured:

• Account Name → Opportunity Account
• Account Address → Opportunity Address
• Primary Contact → Opportunity Contact

This ensures that users do not need to re-enter data each time they create related records.

Considerations / Best Practices

• Only one-to-many (1:N) and many-to-one (N:1) relationships support mappings.
• You cannot map fields between many-to-many (N:N) relationships.
• Source and target fields must be of the same data type (e.g., text → text, option set → option set).
• Keep mappings minimal to avoid unnecessary data duplication.
• Always document mappings in a data dictionary for future maintenance.

Why It Matters for Sales

Configuring relationship mappings in Sales tables (Account, Contact, Lead, Opportunity, etc.) helps sales teams:

• Save time by auto-populating repeated information.
• Maintain data accuracy across records.
• Improve productivity by reducing manual entry errors.
• Ensure consistency across key sales processes like Lead → Opportunity → Account.