welcome to XRM blog

Keep in touch with latest CRM/ERP articles

To remain competitive your organisation must be efficient across the business process spectrum. To do so you need to take sound decisions based on a balance between the cost and risk. To do so you will be heavily dependent on your content management in itself needs...

image
Blog

N: N Relationship In Dynamic CRM 2011

By Makrand Hardey on 4/11/2014

It is the easiest but with most limitation. Use when you only need to know that two records are connected to each other but you don’t need additional details (instances) about the connection. When an entity X is associated to entity Y directly then it forms N: N relationship.

NATIVE  RELATIONSHIP  

Native N: N Relationship can be created by clicking on setting, open solution for customization that contain entity  for which relationship  need to created  with some other entity suppose contact and custom . Click on N: N Relationship of specific entity (Contact) on left Navigation of solution, then click New N: N relationship. New form is opened with default Display option value as “Do not display” on both source and target entity.

 

Before create make sure that Display Option is set as “Plural Name” on both the source and target entity, so that is can be visible on left navigation of both the related entity and click SAVE.

 

By going on contact you will be able to see all the custom entity records and same on going custom entity record you will see all contact records related to it.
 

      

     Figure 1: N: N Native Relationship

Native N: N Relationships Advantages and Disadvantages

  • The main advantage of native N: N relationships are that it can be easily configured and understand.

There are many disadvantages of Native N: N relationship:

  • Cannot build a view through Advance Find that contains columns from both sides of the relationship as it does not contain any instances of relationship.
  • Cannot import data using the Import Data Wizard. For example, if N: N relationship is created between contact and member in CRM. It’s not possible to import a big list of association members (contacts) and get them attached to the associations while importing.
  • Workflow won’t work in case of Native relationship as for example if on change of value of any field on contact form workflow won’t trigger.

 

2.  Manual N: N Relationships

The Manual N: N Relationship is created by adds two components(1:N and 1:N) not used in the native relationship i.e. we  have to relate two entity indirectly with third entity called as intersection entity that contains instances(entity Id , status, createdon, modifiedon value etc.)                          

                                

                                                          Figure 2: N: N Manual Relationship

  •  In this relationship there is a third entity often referred to as “intersection” or “junction” entity that contains the instances (details) of relationship.
  •  Taking an example with Entity X and Entity Y, you need to create a custom entity called something like “Association Membership” which will be intersection entity. If you were building a registration system, you might have contacts and events related with an N: N relationship, and create a custom entity called “Registration” as the intersection entity.
  •  Instead of creating a direct N: N relationship as in Native, you relate the two entities indirectly, by creating 1:N relationships to the intersection record type.
  •  All above disadvantages of native N: N relationship is resolved by manual N: N relationship.

 

 

 

 

  

 

N: N Relationship
Blog Calendar
Blog Calendar List
2024 Apr  18  4
2024 Mar  33  4
2024 Feb  28  3
2024 Jan  8  7
2023 Dec  14  6
2023 Nov  45  5
2023 Oct  118  12
2023 Sep  245  9
2023 Aug  63  7
2023 Jul  31  5
2023 Jun  20  4
2023 May  43  5
2023 Apr  35  5
2023 Mar  98  6
2023 Feb  111  5
2023 Jan  40  4
2022 Dec  94  7
2022 Nov  254  2
2022 Sep  13  1
2022 Aug  28  2
2022 Jun  7  2
2022 May  4  2
2022 Apr  6  2
2022 Mar  2  1
2022 Feb  2  1
2022 Jan  1  1
2021 Dec  4  1
2021 Nov  2  1
2021 Oct  2  1
2021 Sep  12  1
2021 Aug  38  5
2021 Jul  36  4
2021 Jun  1244  5
2021 May  31  3
2021 Apr  2036  3
2021 Mar  189  5
2021 Feb  2142  7
2021 Jan  3106  9
2020 Dec  446  7
2020 Sep  74  3
2020 Aug  685  3
2020 Jul  128  1
2020 Jun  75  3
2020 Apr  69  3
2020 Mar  13  2
2020 Feb  28  5
2020 Jan  34  7
2019 Dec  17  4
2019 Nov  30  1
2019 Jan  23  2
2018 Dec  71  4
2018 Nov  68  3
2018 Oct  18  3
2018 Sep  1152  11
2018 Aug  7  2
2018 Jun  14  1
2018 Jan  68  2
2017 Sep  585  5
2017 Aug  17  1
2017 Jul  17  2
2017 Jun  62  2
2017 May  21  1
2017 Apr  35  2
2017 Mar  135  4
2017 Feb  784  4
2016 Dec  204  3
2016 Nov  833  8
2016 Oct  307  10
2016 Sep  704  6
2016 Aug  39  1
2016 Jun  1876  6
2016 May  110  3
2016 Jan  71  2
2015 Dec  484  6
2015 Nov  4  1
2015 Oct  13  1
2015 Sep  1464  6
2015 Aug  14  1
2015 Jul  128  2
2015 Jun  11  1
2015 May  20  1
2015 Apr  30  3
2015 Mar  80  3
2015 Jan  5335  4
2014 Dec  17  1
2014 Nov  2257  4
2014 Oct  68  1
2014 Sep  107  2
2014 Aug  5280  1
2014 Jul  49  2
2014 Apr  2578  12
2014 Mar  301  17
2014 Feb  220  6
2014 Jan  1510  16
2013 Dec  21  2
2013 Nov  690  2
2013 Oct  256  3
2013 Sep  11  1
2013 Aug  40  3
2013 Jul  214  1
2013 Apr  57  6
2013 Mar  2292  10
2013 Feb  127  3
2013 Jan  343  2
2012 Nov  57  2
2012 Oct  499  10
Tag Cloud
Interested in our services? Still not sure about project details? get a quote