Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
N:N Relationships are otherwise known as many-to-many relationships in Microsoft Dynamics 365/CRM.
They are accompanied by the other two types within the system, 1:N (one-to-many), and N:1 (many-to-one).
A N:N (many-to-many) relationship is used to link many records from one entity to many records of another.
Each side of the relationship will display the various records that are associated with each other as a result through a subgrid.
Behind the scenes, D365 creates a relationship entity that links the records together. This relationship entity cannot be edited, so no additional fields/information can be tracked for the relationship.
The most common N:N relationships are records associated with a marketing list. Accounts, Contacts, and Leads can be on multiple marketing lists and each marketing list can have multiple Accounts, Contacts, or Leads associated to it.
No other information can be collected about that relationship, just the name of the record and the marketing list it is associated to. Using Contacts as an example, when looking at a Contact related marketing list, it shows a sub-grid of Contacts associated to it.
Then, if you look at a Contact record, you can see a sub-grid of all marketing lists it is associated to it.
There are many uses cases where an N:N relationship may make sense:
To set up or alter N:N Relationships in Microsoft Dynamics 365/CRM, follow these simple steps …
Learn more about Relationships in Microsoft Dynamics 365/CRM when you catch-up and click replay on our December Microsoft Dynamics 365/CRM user group webinar, “Best Practices for the Advanced Admin”.
Watch it here, and sign up for the next webinar!
Business Applications communities