Hello.

This time we will explain the concept of association between entities.

1. Associations between entities

In the first place, associations between entities, as the name suggests, are about associating each entity.

Doing this will allow you to display the required information on the form using records in the associated entity.

There are three types of relationships between these entities: [1:N], [N:1], and [N:N].

I hope you understand these three ways of thinking.

1. [XNUMX:N] association

First, let's consider the idea of [1:N] association.

As shown in the diagram above, if the account entity is 1, the contact entity for that company is N.

In this example, there are multiple contact persons for one business partner.

Simply put, the client representatives at client company A are Sato, Tanaka, Saito, Takahashi, etc.

We will reflect this relationship in Dynamics.importantNanohaThings that can only be displayed in subgrids or associated views.

This is because there is more than one related record for an account, in this case a contact.

Therefore, you can select multiple related records.

If you were to actually represent this on a form, it would look like the image above.

Basically, we consider the part in the previous section as the basis, so in this case it is the trading partner entity, which is part 1, [XNUMX:N].

So, as you can see, when you select the Account entity on the site map, the contact person is displayed in the form.

1. [N:XNUMX] association

Next is the idea of [N:1] association.

As shown in the figure above, the number of contact persons is N and the number of business partners is 1, which is the same as the [XNUMX:N] mentioned above.

However, the first and second paragraphs have been swapped.

So in this example, there are multiple contact persons and one business partner.

In other words, it means that "Sato, Tanaka, Saito, Takahashi, etc. are business partners of Company A."

hereimportantThe reason is that,Unlike before, it should be displayed in the search field..

This is because there can only be one business partner for each contact person.

Therefore, you can only select one related record.

This will look like the image above when actually displayed on a form.

In this case, [N:1], meaning N is the previous term, is why we are selecting the Contact entity.

Therefore, as you can see, the name of the company the contact person belongs to is displayed on the contact person form.

4. [N:N] association

Finally, the idea of [N:N] association.

As shown in the image above, we will add a marketing list to the same contact person as N from before, but this time as a new N.

So for "multiple" contacts, there will be "multiple" marketing lists.

For example,

1. We are running Campaign A and Campaign B for Takahashi.
2. We are running Campaign A and Campaign C for Mr. Tanaka.

Above is how your marketing list will look from your contacts' perspective.

To reverse this example,

1. We are currently running Campaign A with Takahashi and Tanaka.
2. We are currently running Campaign B with Takahashi.
3. We are currently running Campaign C for Mr. Tanaka.

These are the contacts from your marketing list.

This means you can associate information from both.

Like 1:N, this relationship can only be displayed in a sub-grid or related view.

The reason is that there is not one marketing list per contact.

Also, there is not one contact per marketing list.

Therefore, you can select multiple related records.

The image above shows the screen from the marketing list.

As you can see, the Contact Associated view is displayed.

Next, the image above shows the screen as seen by the client's representative.

As you can see, the marketing list related view is displayed.

XNUMX. Conclusion

It's conceptual and a bit difficult to understand.

However, once you have mastered it, you will definitely be able to take the first step towards mastering Dynamics 365 and Power Apps.

I am still inexperienced, so I would like to continue to improve myself.