Relationships in Microsoft Dynamics CRM 2013 free online learning tutorials

Summary:Relationships in ms dynamics crm 2011 online Training Tutorials 
                        Not to be confused with relationships/connections as found on the interface level, relationships on the schema level are programmatic.That being said, relationships are very user-friendly; you don’t need to be a database system administrator expert to use and configure relationships between entities.
Microsoft Dynamics CRM supports the following relationships:
  1. 1:N relationships (one to many)
  2. N:1 relationships (many to one)
  3. N:N relationships (many to many)
    can add as many relationships as you want and can also add more than one relationship to the same entity. Example:
you can have a custom entity called Customer and add two fields called Primary Contact and Secondary Contact-both related to the entity Contacts.Finally, another feature to relationships is the ability to relate an entity to itself, which is referred as self-referential. Using this type of relationship, you can use any type of relationship (1:N, N:1 or N:N) to relate an entity to itself.

1:N Relationships:
Figure 23.3 displays the window where you can create a new 1:N relationship. With this type of relationship, the primary entity is the one you are customizing. For example, if you are working with the Account entity, you could use this type of relationship to specify the primary account for another entity, such as Contacts, for which the custom field defined by this relationship will contain only one account
FIGURE 23.3 Creating a new 1: N relationship.
N:1 Relationships:
           With this type of relationship, the primary entity is the one you select. Therefore, the entity you are customizing is the related entity. For example, if you wanted a Contact to have multiple Accounts associated with it, you would apply this relationship to the Account entity.
 N:N Relationships:
           With this type of relationship, there is not one primary entity and another secondary or related entity because they act as both types. For example, you might want to have one Contact related to many Accounts or one Contact related to many Contacts. In a real situation, you could have a Contact with a new person who works for two companies, and each company might have many Contacts apart from this one.

 More Related Articles:
                     Microsoft Dynamics CRM Relationship Patterns,cascading rules
                     Dynamics CRM Customizing Entities Tutorial Part-1 Pdf free download 
                     Microsoft Dynamics CRM Customizing Entities Tutorial Part-2 Pdf free download


Post a comment

Popular Posts