HTML table prints duplicate rows

[Julien2]

Hello,

I have used to create HTML table action to map some fields and display them in an email.

Unfortunately, I couldn't find a value for case action in dynamic content to fill the *From.
Besides, I have used List records action and I was able to fill the *From field.
But as a flow results in the Create HTML table action prints duplicate rows, since it should print only one row.

I want to trigger the following fields in the flow below:

Here are the results:

What I should change to make the HTML table action print only one row?

Any help will be greatly appreciated.

Thank you!

[yashag2255]

Hi @Julien2 

You can create an array first with the filtered values. From your flow, I can see that you are not filtering the values returned from the list records action (because then in the condition branch it would create an apply to each loop and my guess is that the condition is checking the status reason for the get record action). 

Once you filter the records appropriately, add an append to array variable action within the apply to each loop and then create the HTML table outside using the array. I did a sample of detecting and deleting duplicate records from dynamics using the arrays and creating html tables and you can find it here: https://powerusers.microsoft.com/t5/Power-Automate-Community-Blog/Delete-duplicate-records-items-fro...

You might also want to check the status reason filed that you are implying in the condition as it might be looking for an integer value for that particular status reason instead of the label. 

Hope this helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[Julien2]

Hello @yashag2255 ,

Thanks for your reply.

I have created a filter array action to check for the status label records that are equals to "Resolved", then apply to each action inside it an Append to array variable action that contains all the related fields, and I have used the TestArray in my HTML table.
But as a result in the apply to each action, unfortunately, it returns 24 rows which means the HTML table prints again duplicates rows.

Please take a look at what I've modified:

Here are the results:

What did I miss?

Looking to hear from you.

Thanks again!

[Julien2]

Hello @yashag2255,

Any suggestions to solve this issue?

Looking to hear from you.

Thank you.

[yashag2255]

Hey @Julien2 

It will not work like this. you need to add the key value pairs in the html table as shown in the post that I have shared with you. 

Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[Julien2]

Hi @yashag2255 ,

I have changed in the Html table the columns to Automatic and I am already using the "TestArray" variable in the HTML table.

The flow fails when I have switched the columns to Automatic also the apply to each function always returns duplicates rows.
Please take a look at the screenshots below:

What could be the issue here?

Looking to hear from you.

Thank you!

[Julien2]

Hello @yashag2255,
Could you please provide an example similarly to my following issue because the blog you mentioned it's helpful but it looks different to my requirements because i have many fields in the HTML table.

Looking to hear from you.
Thank you!

[yashag2255]

Hey @Julien2 

Can you describe a little more about the scenario that you are trying to build? For some reason, I think there is a disconnect in the condition statement to check the status value. 

If you can share more details, we might be able to assist you better with this. 

Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[Julien2]

Hello @yashag2255,

Sure, please take a look below for the clarification of the flow:

• When a status of a case has been set to Resolved I want to send an email for the user who created the case within his case details in an HTML table template.
• The email template as I mentioned will be an HTML table that requires to display the following fields:
  Case Number, Case Title, Subjects(The subjects field is a lookup from Subjects entity where my subjects exist), Modified On (To show the user the time when the case is closed).

Concerning this condition, I have selected the Status Label from the dynamic content of the action when a record is updated. I didn't face any problem with the condition because as a result, it returns true.

The main problem is that the result of the HTML table, instead of printing the current row that was modified it outputs many rows. So it should only display one row as a result of the selected fields in HTML table.

I hope that you understand my requirements.

Looking to hear from you.
Thanks for your support.

[yashag2255]

Hey @Julien2 

Can you also share the entire flow that you have built so far? 

What is the trigger you are using? In my opinion, based on the scenario that you have shared, the flow configuration should look somewhat like this: 

1. Trigger-> When a record is updated (try using the CDS connector and you can filter on the status value itself) and this one will be for the case entity. 

2. Action-> get record from the case entity, use the identifier from the above action. 

3. Action-> get record from the subject entity and use the identifier from the dynamic content of step 2. 

4. Create HTML table with all the custom columns. 

5. Send email. 

Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[Julien2]

Hi @yashag2255,

Sure, please take a look of my entire flow screenshots:

Services mean the subjects' entity.

I've used List records using the CDS connector to trigger the subjects entity and used it in the HTML table.
After that, when I have switched the value of the HTML table from the TestArray to the value of the list records of the subjects entity, it outputs 3 rows. Where it should print the only one row.
We are very close to solve this issue.

Could you please take a try on my following flow and tell me your results?

Looking to hear from you.
Thank you very much for your support.

[Julien2]

Hello @yashag2255,

Any news about the following issue?

Thank you.

[Julien2]

Hi @yashag2255,

Please, could you assist me to solve this issue?

[Julien2]

Hello @yashag2255 ,

Any suggestions?

Looking to hear from you.

Thank you!

[yashag2255 · Accepted solution]

Hey @Julien2 

Looks like the list records action is getting 3 records which is why the three rows are getting created. Can you shift back to the test array? 

Initialize a test array variable before the condition and then in the condition add a set variable action and in the value part add this: 

[

{

"Case Number" : "selectthecasenumberhere",

"Case Title" : "selectcasetitlehere",

"Service" : "selectthecomposeoutputhere",

"Closed Date" : "selectcloseddatehere"

}

]

Now, add the create html table action and select the variable (do not customise columns) and try this. This should resolve your issue. 

Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[Julien2]

Hi @yashag2255 ,

Thanks for your reply.

I have followed the steps you mentioned and as a result the HTML table output one row.

Unfortunately, when I resolve a case for a record I receive the same emails 3 times, knowing that I have one send email action.

Please take a look at the modifications and the result:

Any idea why I am receiving duplicates emails for the same record?

Looking to hear from you.

Thanks again!

[yashag2255]

Hi @Julien2 

Can you check the flow run history to see how many times the flow was triggered (was it three times?)

Is the send email action in an apply to each loop? Can you repost the entire flow config again? 

Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[Julien2]

Hello @yashag2255, 

Yes it was three times the flow was triggered please take a look here:

No, I have removed the condition from the apply to each action.

Please take a look of the entire flow:

I have tried today, and the flow was triggered twice and I have only solved the case once it's weird.
Here are the results:

Looking to hear from you.

Thank you!

[yashag2255]

Hi @Julien2 

Yes. That is the reason why it is sending multiple emails as the flow is getting triggered multiple times. The trigger you are using is when a record is updated so no matter if any attribute is updated it will trigger and run the flow. 

Now you can go into each run and check what has happened in that particular run and check the condition was satisfied or not. 

I think in the dynamics triggers, you cannot set attributes on the filter or trigger conditions and that is why I recommend building the entire flow using CDS connector. 

Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[Julien2]

Hello @yashag2255,
 

That's right, I have resolved the same case ID once and on each run the condition result is true. Knowing that it should only be triggered once.

Meanwhile, I have created the same flow using the CDS connector(Current environment).
In the first action in the Filtering attributes field, I have entered the Status Label schema name. (Because the flow will run only if this status will be updated).
Please take a look here:

The result of this flow using CDS connector I have received 7 consecutive emails:

Concerning the condition, I was not able to find the label of the status from the dynamic content of "When a record is created, updated, deleted".
Because I should check if the status label is equal to resolved then I will create an HTML table and send an email.

Any suggestion on how to map the label of a field from a CDS connector in a condition?

Looking to hear from you.
Thank you!