Conditional Statement Needs to Check 2 Separate D365 Entities

[saturation]

I have a conditional statement that requires checking 2 different entities, then sets the Company Type if the conditions are true. Here's basically how it goes..

If company type=prospect AND loan stage=terms, set the company type=lead

I'm able to check 1 entity for its value, but I can't seem to figure out how to check 2 different entities before updating the company type value? Can someone help?

[abm]

Hi @saturation 

Could you post your flow screenshot?

Thanks

[saturation]

Here's the flow without the Company entity. It checks the loan entity for a stage, then updates the company type (which you can't see but it's in the update section). But I need it to check the loan entity for a stage, but also check the company type to see if it's a 'prospect' and if it meets both conditions, set the company type to 'lead'

[abm]

Hi @saturation 

Thanks for the screenshot. 

So after the condition under the yes you need to do retrieve the second entity record. Then check the condition for company type. To retreive the second entity you need the Id (GUID) of that record. Have you got any relationship between two entities?

Thanks

[admind365]

Yes, the companyid is stored on the loan record. So basically, connect again except to the company table using the companyid from the loan, check that company type, and then do an update record? I guess I was just confused on whether or not you could combine the conditional statements together rather than doing one, then doing the other...I'm a newbie 🙂

[abm]

Hi @admind365  & @saturation

In this scenario you can't combine in one condition. You need to retrieve it separately. 

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up.

Thanks

[abm]

Hi @saturation  & @admind365 

If the below reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up.

Thanks

[v-alzhan-msft]

Hi @saturation ,

Please refer to screenshot below to create the flow:

Best regards,

Alice       

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[abm]

Hi @v-alzhan-msft , @saturation  & @admind365 

The only issue with the below solution is if the first condition is not satisfied (using the triggered context value) then the next step 'Get Record' is an unwanted round trip to database.

Thanks

[v-alzhan-msft · Accepted solution]

Hi @abm ,

Please refer to screenshot below to create the flow:

 

Best regards,

Alice       

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[saturation]

Thanks everyone! That last solution worked - Putting the conditional inside the first conditional. Exciting stuff!