SharePoint New Item Get Attachment Flow Not Working

[trstrean]

Hello Everyone, 

I'm hoping you might be able to help me understand what I'm missing with a flow I'm working on.  I've done something similar to this working with Power Apps, that does work, but I can't seem to get it working with just a standard SharePoint linked flow.  

Pretty simple setup.  SharePoint list with a flow for when a new list item is created that triggers the flow to notify people of the new item and send them the attachments that were included with the list item.  Attachments range in size so I did include a delay in case they were a little larger, but I'm not even getting to that part of the flow based on my review of the data (see captures).  

Flow indicates success, email is received, but no attachments are included in the email.  I've tried several approaches from YouTube at this point, with most of them matching my setup or me trying their exact approach and no luck (that's where I got the delay suggestion for large attachments).  Image 1 and 2 show the flow setup, and image 3 shows where the get attachment body isn't getting populated with file information.  Again, in my Power App version, this does work, but the setup is a little different on that one.  Step 2 of the flow seems like a strange place to run into a glitch on such a common flow, so I must be missing something really basic.

Any suggestions are greatly appreciated!

   

[ekarim2020]

Hi @trstrean ,

An example of reading list item attachments, see:

🖇️How to Read SharePoint List Item Attachments and Send Them via Email Using Power Automate

Note also the format of the attachments array which uses ContentBytes:

See: 📝Short Notes: The Format of the File Attachments Array for Approvals Attachments, Outlook Email Att...

 

Hope this helps.

Ellis
____________________________________
If I have answered your question, please mark the post as ☑️ Solved.
If you like my response, please give it a Thumbs Up.
My Blog Site

[trstrean]

Thanks for the suggestions.  My flow isn't even getting that far before it runs into problems.  My flow triggers when a new item is created, and the very next step is the get attachments step, and the body output of that step is blank, making every step that follows irrelevant at this juncture.  My suspicion is that if I can resolve the get attachment step, everything else will work and the attachments will indeed get attached.  I just need the output body to populate before I can confirm.  Does that clarify?  

[ekarim2020]

Please check SharePoint List item 23 to ensure that it does contain an attachment:

It seems that item 23 was created but no file attachments were added.

Ellis
____________________________________
If I have answered your question, please mark the post as ☑️ Solved.
If you like my response, please give it a Thumbs Up.
My Blog Site

[trstrean]

Thank you for the suggestion.  I had the same thought since it seemed like the only logical issue, but the item does have an attachment.  I also tried it a few times to see if it worked with a single item, versus having a few attachmens, or different attachment types, and nothing made a difference.  

[ekarim2020]

HI @trstrean ,

For testing purposes, please create the following simple flow:

Make sure that the item Id selected does contain one or more attachments.

Please show the runtime output, for example:

Ellis
____________________________________
If I have answered your question, please mark the post as ☑️ Solved.
If you like my response, please give it a Thumbs Up.
My Blog Site

 

[trstrean · Accepted solution]

Ellis, 

Thank you for the suggestion.  When I went through and started the process you suggested, it did point out the error in the flow!  It turns out the error was with the Power App and the attachment upload process after all.  It was the only thing that made any sense to me from the beginning, and your approach got me to slow down and really focus on it.

Once I got past that, I did actually run into issues with the attachments getting into the email and none of the previously mentioned suggestions worked.  The issue was with the ContentBytes portion. I needed to add the expression," base64(filecontentdynamiccontent) " and then it worked without any problem.  I was getting a bunch of weird errors related to the To: Subject: and Body: not being completed if that helps future people diagnose the issue.