SharePoint calculated column doesn't show value when use it in a n automated email

[garzamalanLCG]

So I have a SharePoint List, and I have 2 calculated columns.

One calculated column is Priority ID, which is a ton of if statements depending on another 2 columns, [Urgency] and [Impact].

The second column is Priority Desc which is equal to 

=IF([Priority ID]=1,"Critic",IF([Priority ID]=2,"High",IF([Priority ID]=3,"Medium",IF([Priority ID]=4,"Low",IF([Priority ID]=5,"Very Low","")))))

(Depends on the other calculated column)

So far so good, now I created a flow to send an email when a specific columns is changed, and that email contains values of some columns of that SharePoint list,

The issue is, the Priority ID value shows in the email, but the Priority Desc value doesn't show in the result email.

Here is a screenshot of the email composition in Power Automate

And the result email looks like this

I have try just adding the field and using an expression with string. Doesn't still no show!

[Pstork1]

I suspect the problem is that calculated columns aren't calculated until after a SharePoint list item is saved.  Since you are triggering the flow based on an item being modified I believe the column calculation won't have taken place yet when you try to send the email.  You'll have to calculate the value in the flow itself if you want the email to contain that value.

[garzamalanLCG]

That was my first though, but the column Priority Id, which does show value in my email, it is ALSO a calculated column, so why does that calculated column shows value but the other doesn't.

I thought about calculating it in Flow, but I mean there has to be a reason why is not showing.

[Pstork1]

Does the change that triggers the flow affect the calculation of one column but not the other?  That would be my assumption.  Or it may just be that PriorityID is reporting the old value that will be recalculated, but the new value can't be calculated because its dependent on Priority ID.

[garzamalanLCG · Accepted solution]

What triggers the flow is column Status.

Priority ID calculates from columns Impact and Urgency, which are columns that does not change, from the initial input.

And so they basically have the same dependability. I'm going to try to depend on Impact and Urgency, instead of Priority, for the Description also, and see if that resolves the issue.

[garzamalanLCG]

I don't know why, but that did it. Using the same main columns instead of using the result of the ID.

[Pstork1]

As I said, its because the second calculated column depended on the first calculated column.  I know priorityID wouldn't actually change after being first calculated, but the system doesn't know that. So the second column isn't calculated until after the first column is recalculated upon save, even though it doesn't change.