PA from Dataverse: Choice list returns the value and not the text in an email.

[CuriousMind]

Hi - In a condition where a choice is true to the choice value from Dataverse, the flow will run where an email is sent. The flow works, but the value is displayed in the email and not the actually choice, which should be "Remote". How do I rectify this? I also need to update the column in which this choice was made and then change its name. How would I do this too?

[v-xiaochen-msft]

Hi @CuriousMind ,

Please get its outputs and copy the column name.

Best Regards,

Wearsky

[LinnZawWin]

Hi @CuriousMind 

Is the Send Task To value coming from the Dataverse trigger or the Get a Row / List Rows actions?

If it is from the trigger, you need to write an expression in this format. triggerOutputs()?['body/column_label']

e.g.

triggerOutputs()?['body/xyz_sendtaskto_label']

You can refer to this blog post for more details.

https://d365demystified.com/2020/12/24/read-optionset-labels-from-cds-dataverse-triggers-or-action-s...

If it is from the Get a Row / List Rows actions, you need to write an expression as mentioned by @v-xiaochen-msft columnname@OData.Community.Display.V1.FormattedValue 

e.g. 

outputs('Get_a_row')?['body/xyz_sendtaskto@OData.Community.Display.V1.FormattedValue']

items('Apply_to_each')?['xyz_sendtaskto@OData.Community.Display.V1.FormattedValue']

You can refer to my blog post for more details about that.

https://linnzawwin.blogspot.com/2020/07/get-lookup-display-name-and-option-set.html

[CuriousMind]

Thank - you. This helped. The variable returns the value. But how do I do the same to take a customer lookup value from another table?

[v-xiaochen-msft]

Hi @CuriousMind ,

I'm confused by the new issue. Could you clarify it?

Best Regards,

Wearsky

[CuriousMind]

Hi @v-xiaochen-msft ,

With your help, I am now able to show the selection made within an option set in the email. Now I would like to show the Customer selected inside the same email as well. This customer is from the lookup column Customer from the Accounts table. If I just select the dynamic customer value, I get the GUID of that row.

[LinnZawWin]

@CuriousMind 

Similarly, you can also get the customer name of the lookup column with the expression _columnname_value@OData.Community.Display.V1.FormattedValue 

e.g. 

items('Apply_to_each')?['_xyz_sendto_value@OData.Community.Display.V1.FormattedValue']

More details: https://linnzawwin.blogspot.com/2020/07/get-lookup-display-name-and-option-set.html

[CuriousMind]

Thank you. But I am having a really tough time here. I simply want to show the label (not the value) of a choice in an email. Your initial recommendation works, but I get emails per row of my data.

What should happen is that the user has to make one of three choices under the column "Send Task To" which is "Remote", "Field", or "Technical". And this needs to show in the email the choice made. My triggers work, it just showing the actual data. Really need your help.

[LinnZawWin]

Can you please elaborate more on "And this needs to show in the email the choice made"?

What is the column name of the lookup for the "the email the choice made"?

Does the following expression helps?

items('Apply_to_each')?['_xyz_sendto_value@OData.Community.Display.V1.FormattedValue']

[CuriousMind · Accepted solution]

Hi @LinnZawWin I have just got it to work. 

This is what I did:

1. From the "Send Task To" column, I created three triggers as per pic1.
2. I initialized a variable and called it PingPong (Pic2)
3. I then set the variable from the output of the trigger by using this expression: triggerOutputs()['body/_neo_sendtaskto_label'] (also Pic2)
4. I then selected the variable within the body of the email.

So the above works for the trigger, now it is pull the customer lookup label and many choices from another "Machine" column. 

Pic1

Pic2

[LinnZawWin]

@CuriousMind 

I am glad you got it working. Can you please mark the Reply that solved your problem as a solution to close this thread? That will be useful for others in the community who come across this thread to identify the solution easily.