Microsoft Dynamics 365 | Integration, Dataverse...

Parent Account - Calculated Field

(0) Share

Report

Posted on by jhendrickson

Hi,

I have built a new entity that is related to the Account entity (Account 1:N Client Engagements). On the Account entity we have a field for Parent Account where we list our channel partners that are responsible for supporting these end users. I wanted to create a calculated field on the Client Engagements entity called Parent Account to pull over the Parent Account field but it isn't available when looking through the Account fields. Any thoughts?

Thanks,

Jeremy

I have the same question (0)

All responses (4)

Answers (0)

LuHao 40,892 on at

Like (1)

Report

Hi Jeremy,

Is the Parent Account field on the Account entity a lookup field? Like the OOTB Parent Account field.

If not, please provide a screenshot of the field property of the Parent Account field on the Account entity.

In addition, you can check the Calculated fields considerations.

Was this reply helpful? Yes No
jhendrickson 15 on at

Like (0)

Report

Hi Hao,

Yes, it is the OOB Parent Account field (lookup) on the Account page that I'm trying to pull onto this custom entity form. I did read through the Calculated fields considerations but still unsure if what I'm trying to do is possible or not. I appreciate your help!

Regards,

Jeremy

Was this reply helpful? Yes No
Suggested answer

jhendrickson 15 on at

Like (0)

Report

I was able to figure this out. Not sure this is the best way but created a calculated string field on the Account field to store the data from the Parent Account Lookup field. Then on the custom entity, I was able to create a calculated field and pull the data from the calculated string field on the Account.

Was this reply helpful? Yes No
Suggested answer

LuHao 40,892 on at

Like (0)

Report

Hi jhendrickson,

Situation 1.

If the field of the Parent Account of Client Engagements 1) is only used to display data and is read-only, 2) it does not need to be a storage field and be edited, and 3) this field in not a column in a view or report, then I would recommend you to display the field through the quick view form.

Please refer to this blog to know how to use the quick view form: https://carldesouza.com/dynamics-crm-quick-view-forms/

Situation 2.

If the Parent Account field needs to be used as a column in a view or report, then we must create a field to store its value, just as you originally thought.

In this case, your solution is correct. We can create a calculated field for the Account entity to display the value of the Parent Account field, and then create a calculated field for the Client Engagements entity to display the calculated field value of the Account entity.

Without coding, this is the best way to go.

Was this reply helpful? Yes No