Microsoft Dynamics 365 Relationships

Microsoft Dynamics 365 Relationships is component which uses to connect entities and make data associate with other one. When one to many relationship exists, relationship uses to maintain data integrity of system, and also uses automate system process.

Entity relationships

In Microsoft Dynamics CRM,  Entity relationships define how records can be related to each other in the database.

Entity relationships or Connections?

In Dynamics CRM, Entity relationships are metadata that make changes to the database. Also these relationships allow for queries to retrieve related data very efficiently. Entity relationships use to define formal relationships that define the entity or that most records can use whereas connections are less formal kind of relationships.

Types of entity relationships:

1. 1: N (One-to-Many): An entity relationship where one entity record for the primary entity can be associated to many other related entity records.

2. N: N (Many-to-Many): An entity relationship that depends on a special relationship entity. Hence sometimes called an intersect entity, so that many records of one entity can be related to many records of another entity.

Create relationships:

1: Navigate to Solution Explorer.

2: Select the entity for which relationship is to be set.

3: Expand the entity and select the type of relationship.

4: In the Relationship Definition section, in the related entity list, select the entity to be related.

5: Select whether this will be searchable to not.

6: In the Lookup Field section, specify a value for the Display Name field.

7: In the Field Requirement list, choose an option to specify data requirements whether it is optional, recommended or required.

8: In the Navigation Pane Item for primary entity section, select the display option, display area, custom label and display order.

9: In the Relationship Behavior section, in the type of behavior list, choose one of the following options:

1. Parental: In a parental relationship between two entities, any action taken on a record of the parent entity is also taken on any child entity records.

2. Referential: In a referential relationship between two entities, navigation to any related records is possible, because of actions taken on one will not affect the other.

3. Referential, Restrict Delete: Similar to referential the only difference is that when child record or any related record exists for a parent record, therefore user can not  delete it.

4. Configurable Cascading: In a configurable cascading relationship between two entities, associated behavior uses with each of a set of possible actions.

10: Save the changes and close the relationship form.

11: After completion of customizations publish them.


Possible Relationship Behaviors:

1. Cascade Active: Perform the action on all active related entity records.

2. Cascade All: Perform the action on all related entity records.

3. Cascade None: Do nothing.

4. Cascade User Owned: Remove the value of the lookup field for all related entity records.

5. Remove Link: Prevent the primary entity record from being deleted when related records exist.

6. Restrict Delete: Perform the action on all related entity records owned by the same user as the primary entity record.

Was this article helpful?

No 0