Customer experience | Sales, Customer Insights,...

How to create the relationship between fields within entities

(0) Share

Report

Posted on by pcss-jean

Hello, I am new in the forum and with D365.

I want to ask how we can create the relationship between fields in entities.

I am setting up a Sales Professional and have added some billing fields to the ACCOUNT entity.

I created the same fields for the OFFER and INVOICE entities and created a field mapping between ACCOUNT and the other two entities. In the generation of offers and therefore of invoices, the fields created remain empty, that is, they do not resume the values that have been inserted in the similar fields within the entity ACCOUNT.

Also unlike other fields, it is not possible to search, the lens does not appear. I have not found documentation to help me solve this specific problem but I am sure that for those who work with Dynamics 365 often, this configuration has been resolved several times.

Thank you.

Jean Paul

I have the same question (0)

All responses (9)

Answers (0)

Suggested answer

LuHao 40,892 on at

Like (0)

Report

Hi partner,

Field mapping will only work if you create a record from +New in the lookup field or +New in the subgrid on the form.

In this scenario, only when the Invoice record is created through the Invoice sub-grid on the Account form, the field mapping will work, that is, the mapped fields of Invoice contain data.

The same is true for Offer entity.

Was this reply helpful? Yes No
pcss-jean 5 on at

Like (0)

Report

Hello,

I ran a test creating an offer from the pipeline, thanks to which I can pick up the products on the list and automatically create an offer.

When I then try to create an invoice from the account as you suggested, recalling the offer, the amounts go to zero and the fields in question are not copied from the account information.

So I tried to create an opportunity, a quote and then the invoice directly from the subgrid of the ACCOUNT entity page but the result is the same.

Do you have any further suggestions?

Thank you.

Jean Paul

Was this reply helpful? Yes No
Suggested answer

LuHao 40,892 on at

Like (0)

Report

Hi Jean,

Before creating Invoice form Account form, have you created the mappings in the relationship?

In the customizations, expand N:1 relationships of Account, edit the relationship between Invoice and Account.

Click Mappings, new a mapping, select the fields.

Was this reply helpful? Yes No
Suggested answer

CRMJetty 3,512 on at

Like (0)

Report

In D365,we will create relationships between to entities by creating lookup fields
For Creating relationships refer this link

https://www.youtube.com/watch?v=VwF9O2AOmEw

I hope, it helps

Thanks

Please mark as verified if the answer is helpful

Was this reply helpful? Yes No
venkatsr User Group Leader on at

Like (0)

Report

Hi,

1)Use lookups for this requirement.

2)If you are loosing values upon creation then you have to enable auditing on those fields and verify it.

Was this reply helpful? Yes No
jeanpaul-pcss 10 on at

Like (0)

Report

Hello Lu, i made it already before.

What look strange for me is that some fileds with same function in different forms have a different name.

For example we have "paymenttermscode" that is the same in Account and Offer forms, but we have "address1_freighttermscode" in Account and just "freighttermscode" in Offer. In any case I match these. What is not very clear for me is:

1.I want to add fileds in Account, for example, or use the predefinite fields.

2.I want to recall some fields from Account in Offer Form.

The relationship N:1 should be made in Account, the primary entity should be Offer or Account?

Why for each new relationship, the Status for me is always "not managed"?

Thank you.

Was this reply helpful? Yes No
jeanpaul-pcss 10 on at

Like (0)

Report

Hello Maulik, thanks for this video.

In my case when i create a new lookup field under Offer, the destination records are not other fields but for example: Account, Ai Model, Article, Task. It seems the menu recall other entities and not fields.

Any idea?

Thanks

Was this reply helpful? Yes No
Suggested answer

CRMJetty 3,512 on at

Like (0)

Report

Hi,

Thanks for your response.

Can you please explain your problem with example?

I hope, it helps

Thanks

Please mark as verified if the answer is helpful

Was this reply helpful? Yes No
LuHao 40,892 on at

Like (0)

Report

Hi Jean,

1. The relationship N:1 should be made in Account, the primary entity should be Offer or Account?

This needs to be based on your business needs.

If an account corresponds to multiple offers, then the primary entity is the account.

If an offer corresponds to multiple accounts, then the primary entity is the offer.

Since the mapping is bidirectional, no matter which entity is the primary entity, the fields will be mapped when creating another entity from one entity.

2. Why for each new relationship, the Status for me is always "not managed"?

It is by design.

Unmanaged customizations are any change you have made to your organization through an unmanaged solution. The system solution defines what you can or can't customize by using managed properties. Publishers of managed solutions have the same ability to limit your ability to customize solution components that they add in their solution. You can customize any of the solution components that do not have managed properties that prevent you from customization them.

Was this reply helpful? Yes No