Many to many N:N relationship is not working with "account" and "contact"

(0) Share

Report

Posted on by Aminovski

Hello everybody!
Actually I am trying to create a new N:N relationship between “account” and “contact”. I wanted to display a subgrid of “contacts” in an “account” from which I can add “contacts” to the “account”. The same “contact” can be added in several account record forms. Unfortunately, the “+” button is not displaying on the “contacts” subgrid so I couldn’t add contacts to any account. I have tryied the same thing between “account” and a custom entity and it does work. The question is, is there any limitation with N:N relationships? (it is not a security role issue because I am a System Administrator)

7128.Capture.PNG

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Alex Fun Wei Jie 33,628 on at

Like (0)

Report

Hi,

You should use connection instead of N:N relationship.

Find the explanation here, using N: N for these two entities will cause you a lots of trouble in future.

Was this reply helpful? Yes No
Aminovski on at

Like (0)

Report

Hi,

Thank you for your answer. Using connections doesn't resolve my problem. I used an intermediate entity instead. But for future purpose, I don't understand why it is not possible to add new N:N relationships between "account" and "contact"???

Was this reply helpful? Yes No
Suggested answer

Patrick Friedrich 395 on at

Like (0)

Report

Hi Amine,

in the subgrid settings on the account form you have to set the N:N entity.
In your case it´s called shareholders. So do not choose contact or company in the subgrid.

I have currently the same setting for another project and I´m facing some issues:

Normally, a contact has one main company he/she works for. Therefore the parentcustomerid field makes sense. If you try to add another company for the same contact - issues will appearas Wei already mentioned.

I have the following problem:

community.dynamics.com/.../754611

And there is also another thread with different solutions:

community.dynamics.com/.../127864

But in my mind, nothing of them works properly. Connections are very basic and not smart I guess. And a custom entity could work but I´m not quiet sure to be honest.

So it depends on what do you want to do with the N:N Relationship?

Hope that helps.

Was this reply helpful? Yes No