Calculated Field Not Working in Flow Condition

(0) Share

Report

Posted on by D365 User 06

Hi,

I have a Calculated Field that takes the value from another field from a related entity. This field is a Choice field. The field name is Approval Status and it has 2 options - Approved & Rejected. My Calculated Field name is also the same, and it will take whatever value this field will have.

My Flow condition is - If Approval Status is equal to Rejected

The resultant action should be - Change the Status of the Record to Inactive

However, looks like the Calculated Field is not working for the condition as my Flow is not running at all. Could it be because the value in a Calculated field is real-time? If so, how should I set this condition?

This is a snapshot of my flow...

Thanks!

I have the same question (0)

All responses (4)

Answers (0)

Community Member on at

Like (1)

Report

Hi Partner,

Yes, Calculated fields have many limitations on the flow.

-- I have a Calculated Field that takes the value from another field from a related entity. you need get value from

A calculated field can contain a field from another entity (spanning two entities – current entity and parent record), so the related entity is parent for current entity.

My suggestion:

--Not using calculated field to get value from parent entity,you can use flow to replace it.

(1)When the choice field from parent record changes, change all related child records status.

(2)When you create new child records, update them based on the choice field of parent record.

And you mentioned that your Flow is not running at all, what's the trigger of the flow?

Could you provide full screenshot of the flow?

Was this reply helpful? Yes No
D365 User 06 70 on at

Like (0)

Report

Thank you for your response, ! You are right about the issue with calculated fields, and using a flow to update child record based on parent record changes sounds like a good option. In this case I guess the problem was in the trigger itself due to which my flow wasnt running at all, as I had used the calculated field entity as my trigger and since calculated fields are updated in real time, the flow dint run. So I tried using the parent entity's original field in my trigger instead, and now my flow is running fine.

Thanks a lot for your suggestions, I agree in some cases flow would be a better option than calculated fields.

Was this reply helpful? Yes No
pratyush369 30 on at

Like (1)

Report

Looks like you are using a optionset field, try using the integer value instead of the option name in the Flow.

Was this reply helpful? Yes No
D365 User 06 70 on at

Like (0)

Report

pratyush369

Yes, I had noticed it and had changed it later on. Thanks for your response.

Was this reply helpful? Yes No