Power Automate Attachments Are Corrupt

[martzj]

Hi,

@trice602 

I am trying to build a flow that will share our organizations scorecard every Monday at 8:00 a.m. The Excel document is located in Sharepoint with a specific Microsoft Teams group. I fairly new to flows but have created many utilizing Lists. This is my first flow trying to attach documents. I tried following other forum posts and ended up on the flow below. While the email does send when tested, the attachment is corrupt and won't open properly.

[trice602]

Hi @martzj ,

Here's my successful test flow.  I did another test to try and duplicate the issue and also was able to create the error.  So, in the error test, I tried to send a file (using a file name that didn't exist) with my content bytes and I got the error as expected.  Then I corrected, and retested, attachment opened from email.

So in my test I was sending a file named (and hard-coded) as "Daily Summary.xlsx" which did not exist - I have a space between Daily Summary.  Error occurred.

Next I fixed the file name and retested.  Success.  "DailySummary.xlsx".

Here's a couple of ideas to help you get going this morning:

1)  If the file name is the same every time, hard-code it and validate your flow works.  If the file name does change, hard-coded for testing and we can circle back and get the dynamic file name - but validate your flow works with an attachment that can be emailed/opened.

2)  I don't think you need the base64 expression for the content bytes.

[martzj]

@trice602 

So I hard coded the file name, picture below and used the dynamic content and selected "File Content". The email still sends but the file is corrupted. If there is a space between Test and Attachment do i need to add a "_" between them? Also, after selecting "File Content" and saving the flow, it autoconverts it to base64.

I am at a loss. I am following all the forums/instructions I can find but still wont work. I tried using the same flow on several different documents (Word, Excel, etc.) and of course changing all the path locations, etc. and still all the files are corrupt.

This is error message i receive. 

[trice602]

Hi @martzj ,

Thanks for sharing, that's helpful!  So the issue is you are trying to send (and open) a file that doesn't exist.  Notice the file name is not test attachment.xlsx but rather test attachment (002).xlsx.

With this flow, if the file doesn't exist, it gets created.  Go into your SP folder and you will see a file named test attachment (002).xlsx that is in fact corrupted.

I can't remember off-hand if the space is removed or not automatically, but please look at the output of get file content and you can see the file name that is retrieved (shown below).

[martzj]

@trice602  I really appreciate your help. I still get the same result. I created a whole new Excel file and saved it in a different Sharepoint Team group. I included the flow below. The document is not open and there is only that file visible in Sharepoint. If this doesn't work, is there any way to configure the flow to attach the document?

[trice602]

Hi @martzj ,

Sorry to hear this.  Please look at my original solution.  As stated, you do not need the base64 expression for your file content.  Please duplicate my flow.

[martzj]

Hi @trice602 

UPDATE BELOW

I replicated your flow and receive the same result. 

This is what it looks like before I hit the save button on the flow.

The moment I save the flow, the "File Content" is converted to base64, see below. I am not doing it myself but rather the system is doing it. I don't know how to stop it from doing that. 

I then result in the error message above when I try to open the attachment

I even reverted back to the original view and it shows this. However, still results in same error message

[trice602 · Accepted solution]

Hi @martzj ,

I am not sure why this is occurring, but I do not that the new designer has issues with the action properties; sometimes they will not update after changing.  Because this flow has only 2 actions, please start from scratch and build a completely new flow.  

[martzj]

Hi @trice602 

Thank you. It worked. I built the flow using the old view and it worked. What's weird is that using the new designer the flow worked when selecting a document from my one drive but not from Sharepoint. However, using the old designer it works for both One Drive and Sharepoint.

Thank you again. I appreciate your support and patience. I was starting to thinking I was crazy that the simple flow wasnt working

[trice602]

Nice!  It's not you, it's the new designer still getting developed/repaired.  When in doubt, go to classic and verify.  I LOVE the new designer but as the old saying goes, "trust but verify".

I have also spent hours trying to figure out something basic and simple before.  Now I go to classic immediately on errors that I know should not occur.

[Nivedhana]

I was facing the exact same problem and switching to old designer and recreating the flow worked for us. Thanks!

[Myovanni]

I have de same problem in all your steps, thank you for resolve

[bsfegade]

This works in new designer too.

[bsfegade]

This works in new designer too

[bsfegade]

@marmar @trice602  New designer adds extra double quote when filecontent is selected.
if we remove extra double quote, it works in new designer too

[gstavropoulos]

Hi all!

my case is that the attachment inside my e-mail doesn't have a unique name, it is dynamic, and it is supposed to be uploaded by a different user each time.

When i m trying to test with my own onedrive/sharepoint attachment i am still getting the corrupt file error ( when i open the email attachment i notice that the attachment file name is changed by default, i guess because it is saved in onedrive/sharepoint). How can i fix this issue?  Ideally it should attach from different users each time.

Can you please advise accordingly?

Many Thanks in advance 

[gstavropoulos]

Latest update:

The updated filename is correct now (from Sharepoint) but it is still shown as corrupt when I am trying to open it as a mail attachment. I tried the previous recommended attachment formats but didn't work.