web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Service | Customer Service, Contact Center, Fie... / Best Approach for N:N ...
Service | Customer Service, Contact Center, Fie...
Suggested Answer

Best Approach for N:N Accounts & Contact

(0) ShareShare
ReportReport
Posted on by Abbod Hamwi 587

Hi,

So far, what is the best approach in case we have one contact to be linked with multiple accounts, or one account has multiple contacts, is there an OOB method, should I create N:N Relationship

I have the same question (0)
  • Suggested answer
    a33ik Profile Picture
    a33ik 84,331 Most Valuable Professional on at

    Hello,

    You can either create custom N:N relationship or use OOB Connections.

  • Community Member Profile Picture
    Community Member on at

    Can anyone further elaborate on this N:N relationship setup? We would like to go for this approach too, but not really clear how to set it up.

    Many thanks for your support and feedback upfront.

    KR,

    Charlotte

  • Suggested answer
    a33ik Profile Picture
    a33ik 84,331 Most Valuable Professional on at

    Charlotte,

    Check this post that describes connections - www.crmsoftwareblog.com/.../

  • Suggested answer
    Fubar Profile Picture
    Fubar 2,761 on at

    It depends on exactly what you need to do:

    • Native N:N - quick and easy
    • Manual N:N (you create the intersect entity): used when you need to capture additional information on the intersect entity.
    • Connection Roles:  out of the box capability to link different records specifying a Role, and optionally start end time for the relationship.  But is more difficult for users to make the connections than N:N (particularly with the Unified Interface), as it has a more complex data structure can be more difficult to report on.  Huge benefit is being able to link records from many different entity types and have them appear in the one subgrid.
  • Community Member Profile Picture
    Community Member on at

    Hi,

    we would like to opt for the manual N:N relationship, as dual write to F&0 will also need to be working....

    And if I understood correctly F&0 is setup with N:N as well...

    Could you provide me further information upon this N:N relationship? What intersect entity do we set up best? Also Party?

    and upon the integration/dual write feasibility to F&O?

    Many thanks upfront for your help

    KR,

    CRM cosultant

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Service | Customer Service, Contact Center, Field Service, Guides

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 57 Super User 2025 Season 2

#2
Daniyal Khaleel Profile Picture

Daniyal Khaleel 34 Most Valuable Professional

#3
Scott Jackson UK Profile Picture

Scott Jackson UK 22

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans