locked
Use of N:N relationships RRS feed

  • Question

  • Hi
    Can anyone tell me the benefits of adding N:N Relationships over 1:N or N:1
    Thanks, Aarch
    Thursday, May 7, 2009 8:19 AM

Answers

  • Hi Aarch,

    it is easier to add records and it is easier to add more than one record in one step.

    But it is not possible to add additional attributes to that relationship to have more specific information about that relation, so there are not that many situations where you can use N:N relationships.

    Best regards,
    Jürgen
    Jürgen Beck

    Dipl. Kfm./Wirtschaftsinformatik
    MVP, MCSD.NET, MCITP DBA, MCDBA, MCSE
    Microsoft Certified Business Management Solutions Professional
    Microsoft Certified CRM Developer
    Microsoft Certified Trainer

    ComBeck IT Services & Business Solutions
    Microsoft Gold Certified Partner
    Microsoft Small Business Specialist

    Developing & Supporting Business Applications from small business to big enterprises covering scores of sectors

    http://www.combeck.de
    Thursday, May 7, 2009 8:29 AM
    Moderator
  • Hi,
    There are two ways in which you can create a N:N relationship

    • Native N:N relationship


    Microsoft Dynamics CRM automatically creates N:N relationships between two
    eligible entities. This type of system created N: N relationship utilizes a “hidden”
    intersect entity
    • It is not available for inclusion in workflow rules
    • It cannot be customized


    • Manual N:N relationship


    This type of N:N relationship is actually a combination of two N:1 relationships
    that share a common intersect entity.The benefit of creating a N:N relationship in this manner is that you can also add
    custom attributes on the intersect entity.

    And to choose 1:n over n:n or vice-versa depends on the scenario !

    Regards,
    Nishant Rana
    http://nishantrana.wordpress.com
    • Marked as answer by Aarch Thursday, May 7, 2009 9:29 AM
    Thursday, May 7, 2009 8:43 AM

All replies

  • Hi Aarch,

    it is easier to add records and it is easier to add more than one record in one step.

    But it is not possible to add additional attributes to that relationship to have more specific information about that relation, so there are not that many situations where you can use N:N relationships.

    Best regards,
    Jürgen
    Jürgen Beck

    Dipl. Kfm./Wirtschaftsinformatik
    MVP, MCSD.NET, MCITP DBA, MCDBA, MCSE
    Microsoft Certified Business Management Solutions Professional
    Microsoft Certified CRM Developer
    Microsoft Certified Trainer

    ComBeck IT Services & Business Solutions
    Microsoft Gold Certified Partner
    Microsoft Small Business Specialist

    Developing & Supporting Business Applications from small business to big enterprises covering scores of sectors

    http://www.combeck.de
    Thursday, May 7, 2009 8:29 AM
    Moderator
  • Thanks for the reply Jurgen,

    but this "adding of  records and it is easier to add more than one record in one step" can be done usin 1:Nor n:1 also right.
    Thanks, Aarch
    Thursday, May 7, 2009 8:31 AM
  • Hi Aarch,

    the adding of a N:N-relationship creates a new relationship-record, the adding of a (N:1-1:N)-relationship needs an existing relationship-record.

    But usally N:N-relationships are not that useful many people think because it is not possible to add additional columns or to use it in workflow rules.

    Best regards,
    Jürgen
    Jürgen Beck

    Dipl. Kfm./Wirtschaftsinformatik
    MVP, MCSD.NET, MCITP DBA, MCDBA, MCSE
    Microsoft Certified Business Management Solutions Professional
    Microsoft Certified CRM Developer
    Microsoft Certified Trainer

    ComBeck IT Services & Business Solutions
    Microsoft Gold Certified Partner
    Microsoft Small Business Specialist

    Developing & Supporting Business Applications from small business to big enterprises covering scores of sectors

    http://www.combeck.de
    Thursday, May 7, 2009 8:43 AM
    Moderator
  • Hi,
    There are two ways in which you can create a N:N relationship

    • Native N:N relationship


    Microsoft Dynamics CRM automatically creates N:N relationships between two
    eligible entities. This type of system created N: N relationship utilizes a “hidden”
    intersect entity
    • It is not available for inclusion in workflow rules
    • It cannot be customized


    • Manual N:N relationship


    This type of N:N relationship is actually a combination of two N:1 relationships
    that share a common intersect entity.The benefit of creating a N:N relationship in this manner is that you can also add
    custom attributes on the intersect entity.

    And to choose 1:n over n:n or vice-versa depends on the scenario !

    Regards,
    Nishant Rana
    http://nishantrana.wordpress.com
    • Marked as answer by Aarch Thursday, May 7, 2009 9:29 AM
    Thursday, May 7, 2009 8:43 AM