Richard

Hmmm…help me understand your scenario better and I’ll see if I can help out. Starting with your 1:N from Order to Circuit Design, you’re saying a field on Order called Connection A gets populated to Circuit Design. Is that through a field mapping? Then, are you saying you’d like to have a field from Circuit Design (Connection Z) map back to and auto-populate a field on Order? If the relationship from order to circuit design is 1:N, how will you map fields back from circuit design to order?

Is there a third entity somewhere playing the role of the intersection entity between the two?

Any help or suggestions?

Because you seem to know and understand an awful lot about relationships, I’d like to ask yoiu a question about the manual approach. I have created this kind of relationship for 2 tables: human resources and the languages they speak with the extra field containing information about the level on which they speak it. But now with the advanced find view I have a problem when I want to find human resources that speak eg English on an excellent level and French on a basic level. I chose the language and the level and group them with AND, do the same with the other language, and then these two groups I group again with an AND. I think that the advanced find is looking for one record that responds to all these conditions which of course is impossible. But I don’t know how do construct it differently and get the results I want. Do you have some advice on this?

As far as I can tell, there’s no significant differences between 4.0 and 2011 regarding the issue you asked about: there are two ways to create an N:N relationship:

1. the native approach is easy and works fine for plenty of things, but there’s no intersection entity so you can’t track anything other than whether there IS a relationship or NOT.

2. the manual approach requires 2 1:N’s, and while a little more time-consuming (less so in 2011!) it gives you more information since you have the intersection record.

I am trying to create a many to many relationship between an account and a custom “deal” entry. I would like to track things like “interest level” that are about a particular deal-account relationship. It sounds like in dynamics 4.0 i’d need to create an intermediate entity with fields such as interest level and relate this entity to both deals and accounts in two 1:N relationships. Does this advice still applies to dynamics crm 2011 or have there been improvements with the N:N relationship that would allow me to accomplish this “natively?”

MP