Flow send email for every row in table

[frixel]

Hello,

I have this flow but it send for every row in the table a email.

What do i wrong?

I want that the flow send one email with the HTML table in it.

[efialttes]

Hi!

Please move 'Send an email' out of the apply to each and just after 'Create HTML table'.

Hope this helps

[frixel]

Hi @efialttes 

Send email is in the condition because it only send if the condition is true.

So, i don`t understand what you means. 

[efialttes]

Hi!

According to the screenshot you shared, action 'Send an email' is inside one of the branches of a Condition. But please note the Condition is inside 'Apply to each 2'. So, 'Send an email' is inside an Apply to each.

This means if the Apply to Each iterates through 100 items, and the Condition is evaluated as true for 80 of them, 80 emails will be sent. Since you expect a single email,  you need to move it out of the Apply to each

Hope it makes sense

[frixel]

@efialttes 

But in that case the is alway`s send a email, even when the rows are empty.

[efialttes · Accepted solution]

Now, on the evaluation you need. I guess yo wanna buid an HTML table with not all rows from the Excel table, but with the ones that match certain criteria. You can achieve this requirement by three different approaches:

1.- by means of an ODATA filter defined inside 'List rows present in a table' (Filter query input)

 Next, 'Create HTML table' (assign as its input 'List rows present in a table' output), then 'Send an email'

2.- By means of a 'Filter array' action block(assign as its input 'List rows present in a table' output). Next, 'Create HTML table' (assign as its input 'Filter Array' output), then 'Send an email'

3.- By means of an 'Initialize variable' action block (type array), an 'Apply to each' just after 'List rows present in a table', a Condition inside it, and on its true branch, an 'Append to array' action block. Next, after 'Apply to each', add 'Create HTML table' (assign as its input the array variable),  then 'Send an email'

Option#3 is the most intuituve, but poor in terms of performance

Now, if you want to avoid sending the email when nr of matches is zero, you need to add a Condition action block just before 'Create HTML table'. The condition shall evaluate lenght of the input you are about to assign to 'Create HTML' table. If lenght is zero, 'Terminate' action block. 

Hope this helps

[efialttes]

Now, if you want to avoid sending the email when nr of matches is zero, you need to add a Condition action block just before 'Create HTML table'. The condition shall evaluate lenght of the input you are about to assign to 'Create HYML' table. If lenght is zero, 'Terminate' action block. 

[frixel]

@efialttes 

I make the flow now as under.

It likes it works now fine. Is it so as you mean?

[efialttes]

Hi!

I guess your length() based expression is length(body('Filter_array')) right?

If so, that's the idea

Great job!

Just curious on why you left empty 'Filter array' condition rule right side. So you wanna skip all rows with empty ID, right? If so, I would rather use the following approach

Left side:WDL expression

empty(item()?['ID'])

Right side: WDL expression

false

Operator: equals

Hope this helps

[frixel]

@efialttes 

What do you mean with:

Just curious on why you left empty 'Filter array' condition rule left side

I think you mean this?

to make as

Edit:

Operator must be: NOT equals i think

[frixel]

@efialttes 

I tested it but now always send a email even as the ID is empty.

[efialttes]

Sorry, I was not referring to 'Condition 2' action block. I was referring to 'Filter array' action block, , the right side (not the left, my mistake) of its condition rule. Every 'Filter array' has a condition rule inside. Its right side is empty.

Hope this helps