Power Automate - Dynamic E-mail Content - Dataverse

[JohanGermishuys]

Hi,

I'm trying to do the following. I'm trying to build a single flow that can send out various types of e-mails. As an Input, I'm imagining using something like this:

"I am {Field A}, can you please fix this. This is related to {Field B}.
Please address by {Field C}."

or

"I am {Field D}, can you please fix this. This is related to {Field E}.
This could look completely different.
Please address by {Field F}"

What would be the best way of achieving this. I'm picturing using some form of Regular Expressions to replace the "Field A" with a piece of code. Something like this "first(body('List_rows')?['value'])?['crfaa_prospectnumber']".

Any hints or suggestions would be greatly appreciated.

[abm]

Hi @JohanGermishuys 

You could use the replace but there are other ways to achieve this.

Believe you have an IF condition to determine which content you want to use. Declare a variable string data type called 'EmailBody'. So under the IF condition set the EmailBody text and mappings. Finally under the Send Email action step map the string EmailBody.

Thanks

[JohanGermishuys]

The challenge I have is, I'm trying to address several dataverse tables with 100's of attributes. This is why I'm trying to do this in a dynamic way.

[abm]

Hi @JohanGermishuys 

How you going to determine which email body you need to use? 

Thanks

[JohanGermishuys]

That’s is one of the inputs that other users will be provide to the workflow. They can determine what the body will look like.

[abm]

Thanks for your reply.

"I am {Field A}, can you please fix this. This is related to {Field B}.
Please address by {Field C}."

or

"I am {Field D}, can you please fix this. This is related to {Field E}.
This could look completely different.
Please address by {Field F}"

Like you mentioned above still you need to determine which field is passed. So I am assuming you need some sort of IF condition to evaluate what are the fields you need to map for each condition. 

[JohanGermishuys]

When the user start this workflow, they will choose the dataverse table from a list, another input is a unique ID / Record ID that they'll provide as well as an input.

Based on that input, I'll know which table to access. I will also be adding inputs for the "e-mail" mask that they will identify, and those fields will be from that table.

[LinnZawWin]

If the user is going to provide the unique ID / Record ID, you can dynamically query the record from a different table with Get a row by ID action instead of List Rows.

The harder part is when you try to dynamically get the value of the columns with different names from the different tables.

[abm]

Hi @JohanGermishuys 

Passing the GUID as an input is not very user friendly. Still you need to determine which email you want to generate based on the table. Can't you think about adding a field called 'Send Email' in relevant entities and from the user interface when user select 'Yes' you could generate the relevant email. You mentioned there are more than one table here, so still you need to determine which table and email. Can't see any easy way to do this.

Thanks

[JohanGermishuys]

I believe I have solved pulling the individual values from the table.

By using the "Select Columns" option, I can limit it to a single column at a time. The next challenge will be performing a "Do Loop" on the various {} fields within the masked e-mail body.

[abm]

Hi @JohanGermishuys 

This is where I mentioned the IF condition to determine what type of email body you want to construct, so that you can directly map the fields under.

Thanks

[JohanGermishuys]

Hi, this is for others trying to do this.

Here are the steps I used:

1. Create a variable for the body mask I want to use. (I'm using {} to identify the field names).
2. Create a variable for the "Source Table Name"; I used the "peek code" feature to get it.
3. Use a "Compose" the split the field up fields using the '{' character into an array.
4. We then loop over the array and split the field using the '}' character which gives us the Field name we need to use for running a query;
5. We then limit the query to a field at a time, and we can get the result.
6. Using the field, we looked for, and the query return we can replace this in our variable and update the body of the e-mail.

 

[abm]

Hi @JohanGermishuys 

Thanks for your reply. Here your table name is also passed as Dynamic. If so you will struggle to map it. For each table the results are different. Hence I suggested the IF condition for each table. 

[LinnZawWin]

@JohanGermishuys 

Just to understand a bit further why you need to loop through all the fields to "List Rows", can you also show me the "Filter rows" of the "List Rows" action?

[JohanGermishuys]

This is to limit it to a single record to return the data from it.