Problem with resulting attachments in email

[Tmalonson]

Okay, so here the gist; I've managed to build the entire flow, it functions up until it send the email.
We have a SP List of employees, with a secondary list of individual files per employee.
I've created a flow to find and return all attachments under a specific employee's name (searched for during the trigger).

The flow searches properly, returns the correct count of items for that employee, gets the attachment contents, then appends it to an array variable using the following code.

{
  "name": "@{items('Apply_to_each')?['DisplayName']}",
  "contentBytes": {
    "$content-type": "@{body('Get_attachment_content')?['$content-type']}",
    "$content": "@{body('Get_attachment_content')?['$content']}"
  }
}

The Problem: When it goes to send the email, it isn't including the attachments properly. They are attached as a single, non-descript file that, when opened, is a very long string of code.
I can only assume that the problem has to have something to do with the array variable. (Maybe inside of the ('Apply_to_each')?)
I can't be sure.

This was the only part of the flow that I was unsure of how to do, so I googled a solution on how to compile the data. 
GetAttachment Content(Append to Array) was the only thing I found, but it just doesnt seem to format the items correctly.

Could someone help me correct this?

[v-qiaqi-msft · Accepted solution]

HI @Tmalonson,

I have a simple demo for your reference:

[Fintech]

Hello! I have the same problem. 

I have a list in Sharepoint.  The flow searches properly, returns the correct filters. It functions up until it send the email. 

For all attachments from a single ID I want to send a single email. 

The problem is it attaches all the files from all the IDs. 

Please, help me how can I correct that?

[Tmalonson]

Ah, this is a much easier thing to solve.
I actually solved the whole problem myself and thought I had updated all relevant forums.

Forgive my lack of demonstration, I have a flight at 6am. You get what you get, lol.

ForEach(Get item) get attachments —> compose(create array) then set the Variable to be attached --> send email.
It sounds like your attachments are already attaching correctly, so I'll skip that part.

Then under the ForEach settings there is an optional rule that it may recommend called duplicity (I think). 

Basically, it only allows one existing instance of a variable set inside occurance of the for each.

That  nested ForEach and optional setting should correct your problem.

[Fintech]

Thank you for you answer! But this it doesn't solve my problem. I want the flow to run with weekly recurrence, not when an item is created. With recurrence, after action Get items, add Get attachments with ID from Get items but is into For each. I think this is may problem and i don't know how to avoid For each. When it goes to send the email, attach all attachments from each ID. Please, see attached my flow run. Could you help me, please? I tried to find a solution on google, but I didn't succeed.

[Tmalonson]

Okay, so reviewing your picture, you have it set up like I had mentioned.
ForEach(Item)>Get Atttachments
For Each(Attachment)>get content>Append to array variable *Close foreach(attachment)*
For Each(item)>send and email

The problem your describing is that the variable isn't being refreshed foreach occurrence.
Right click on your Apply to each 2 header and go into the settings.
There should be a setting called duplicity. Turn it on and set it to one.
That will reset your variable at the end of each cycle, dumping the attachments from the previous get items.

This should result in:

For Each(individual item) > get attachments(and append content to variable) > then send an email
After which, it should clear the variable input, leaving a blank slate for the attachment content of the next item to be sent out,

[Tmalonson]

Did that last reply solve your problem?

[Fintech]

Hello! Unfortunately, it didn't solve my problem. At the moment, I haven't found a solution.

[Tmalonson]

The problem was that it was including all files processed within the flow, right?
And that it wasn't emptying them after it sent the email to re-start the loop?

If that's the case, here is the gist of the problem. It isn't dumping the attachments from the previous loops. This means that it continues to append to the array variable until the loop ends.

The easiest solution is to add a Set Variable() action immediately after your Send an Email V2() action inside of the For Each().
Input a function to set the variable fx = null

Then, after it sends each email, it should empty the variable and prepare it for the next loop.

So, the bulk of the flow should look/function like this:
Get Items >
        For Each <Item>(Get Attachments)

              For Each <Attachment>(Get Attachment Contents) -> Append to Array Variable -> *Close For Each Att.*

        Send an email V2(containing the variable in attachments)

        Set Variable to(null) ->*Close For Each <item>*

This should reset the array variable to null at the end of each loop, effectively preventing the flow from attaching them to the next email.

There may be some complication of it not wanting to use something stored within a FOR EACH loop.
If that's the case, there's normally a way to circumvent it using come compose actions to carry the information over, but for now, lets just try using the variable and see if that works.
I would add examples, but I have since decommissioned my flow due to some threshold problems with the list it interacted with. The best I can do is reference my old screenshots in numerous threads on here.

Here's an example, I modified a current flow to demonstrate what it should vaguely look like.
Note: fx = (null) is just a place holder, it seemed more helpful than a pink box saying undefined; you'll need to open the function panel and type in null to create a valid input.

[Fintech]

Your solution solved my problem. Thank you very very much!

[Tmalonson]

Glad I was able to help!
Honestly, I am pretty novice at all of this myself (my degree is in business, not computer science); but feel free to @ME anytime for help. I'm pretty good at problem solving. 👍