cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Frequent Visitor

How can we fetch the grand child look values from dynamics 365 entity

Hi,

In dynamics 365, I have 3 entities (E1, E2, E3),  E2 has a lookup column from E3 and E1 has lookup column from E2.

I have an update trigger on E1 and I need to fetch the value of E3.

 

can anyone help me to get this done?

 

Thank You.

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Super User
Super User

Re: How can we fetch the grand child look values from dynamics 365 entity

@Vivek_Pande - Yes, this can be done. If these are truly 1:1 related records, then the steps are simpler. If they are 1:N (one to many), then it gets a little more complicated, but doable.

 

For 1:1 - If your trigger is kicked off from E1, then add another step for E2 of "Get Record", choose the entity, then use the prior steps fields to get the GUID for the "Get Record" step. Repeat this for E3 from the E2 "Get Record" step.

 

To get the GUID for the E1 record, here is an example: Say E1 equals the "Account" entity and E2 is also the "Account" entity. How they are linked is using the "Parent Account" field on the "Account" form. 

 

E1 is the Parent account and E2 is the Child account.

 

In Power Automate, the trigger kicks off when the Parent account is updated. The next step is "Get Record", choosing the Accounts entity. In the "ID" field, use the Dynamic Content field from the trigger step of "Account". It should have a description stating is the unique identifier which is the GUID.

 

Now, you should be able to reference each entity in any subsequent steps.

 

If your setup is Parent, many children, many grandchildren, then the approach would be more complicated.

View solution in original post

1 REPLY 1
Highlighted
Super User
Super User

Re: How can we fetch the grand child look values from dynamics 365 entity

@Vivek_Pande - Yes, this can be done. If these are truly 1:1 related records, then the steps are simpler. If they are 1:N (one to many), then it gets a little more complicated, but doable.

 

For 1:1 - If your trigger is kicked off from E1, then add another step for E2 of "Get Record", choose the entity, then use the prior steps fields to get the GUID for the "Get Record" step. Repeat this for E3 from the E2 "Get Record" step.

 

To get the GUID for the E1 record, here is an example: Say E1 equals the "Account" entity and E2 is also the "Account" entity. How they are linked is using the "Parent Account" field on the "Account" form. 

 

E1 is the Parent account and E2 is the Child account.

 

In Power Automate, the trigger kicks off when the Parent account is updated. The next step is "Get Record", choosing the Accounts entity. In the "ID" field, use the Dynamic Content field from the trigger step of "Account". It should have a description stating is the unique identifier which is the GUID.

 

Now, you should be able to reference each entity in any subsequent steps.

 

If your setup is Parent, many children, many grandchildren, then the approach would be more complicated.

View solution in original post

Helpful resources

Announcements
firstImage

Super User Program Update

Three Super User rank tiers have been launched!

firstImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

firstImage

Join the new Power Virtual Agents Community!

We are excited to announce the launch of Power Virtual Agents Community. Check it out now!

firstImage

New & Improved Power Automate Community Cookbook

We've updated and improved the layout and uploading format of the Power Automate Cookbook!

thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

Top Solution Authors
Users online (8,322)