Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2023 Release Wave 1Check out the latest updates and new features of Dynamics 365 released from April 2023 through September 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I have a case entity, it is linked to a customer entity, (i.e. a case has a customer). The customer is linked to a location entity which contains a numerical field.
Case >> Customer >> Location value
Is it possible to pull the "Location value" back to the Case form to use as a variable in a calculated field?
Thank you for your time,
I don't think you can do that because of the limitation of calculated field. You cannot use 2nd level related entity in it. Please take a look at the limitations: www.thetindog.com/.../calculated-field-limitations
How about create calculated field on Customer entity to pull location value
You can access parental fields via the Lookup field to the parent entity, such as <LookupFieldName>.<FieldName>. This is not possible with multi-entity Lookup fields like Customer which can be Account or Contact. However, some entities have individual Lookup fields for a specific entity, such as ParentAccountid.<FieldName> or ParentContactid.<FieldName>.
Now create calculated field on Case entity to use the calculated field on Customer entity to pull the location value on Case
Hi Oliver McErlane,
Yes, it is possible. You can bring location value.
Syntax: logical name of the lookup. logical name of the column
Is it possible that you could send a screenshot of what that would look like?
Business Applications communities