PDF attachment corrupt

[beescreamer]

Hello,

I have built a flow that when a file is created in SharePoint, it takes the file and sends the file as an attachment in an email. The pdf does not open and says its corrrupt. I have checked out a lot of the solutions and none of them seem to work, or there are different parts in those flows that I don't have. Didn't think it would be this hard to attach an attachment.

Here is what my flow looks like:

File Content Properties:

Email Attachment properties:

ContentBytes: base64(body('Get_file_content')) 

Thanks for the help!

[Pstork1]

Don't use BAse64() to encode the file content when you add it as an attachment. Since you retrieve the content in the step previous its already in the right format. Just use the file content dynamic content for the ContentBytes:  Also make sure that the filename you are using includes the correct extension.

[beescreamer]

I use the dynamic content File Content, but when I save the flow it changes it to Base64(). So I removed the Base64 so it only reads body('Get_file_content') and now the pdf opens but it is blank. it is just white pages.

file extension is correct, I am using dynamic content File Name with Extension, and the attachment looks correct when it comes through.

[Pstork1 · Accepted solution]

I think it may be a bug in the new designer.  Try switching to the legacy designer using the context menu in the upper right corner.  I did a test build of the same flow you did and when I did it in the new designer it didn't work. But when I switched to the legacy designer it worked as expected.

[Paulie78]

Also try removing the double quotes after ContentBytes, so it is like this:

{
  "Name": FilenameDynamicContent,
  "ContentBytes": @{body('Get_file_content')}
}

Instead of:

{
  "Name": FilenameDynamicContent,
  "ContentBytes": "@{base64(body('Get_file_content'))}"
}

I agree with @Pstork1 that the problem is probably the new designer. But try removing the double quotes. That may cause the content of Get_file_content to become stringified.

Blog: tachytelic.net

YouTube: https://www.youtube.com/c/PaulieM/videos

If I answered your question, please accept it as a solution 😘

[Pstork1]

I recreated the problem in the new designer and was successful using the legacy designer. Its definitely a bug in the new designer. I've reported it to the product team and they are looking into it. In the meantime switch back to the legacy designer and it will be fine.

[beescreamer]

Thank you, this did make it work. I had seen that solution somewhere else, but didn't see the classic view anywhere and thought maybe it was suggested in an older post. Decided to look harder after you suggested it. Thanks again.

[PC_Dokter_H]

I just encountered the same bug. 2 hours of debugging. Changing body, changing Base64(Body/content) changing to Base64ToBinary like explained in this video: Add multiple attachments to an email in Power Auto... - Power Platform Community (microsoft.com) NOTHING WORKED!!! AND then, out of all things,... it was the NEW DESIGNER that was the issue?!?!?!

My issue is solved because of this comment. If anyone has Microsoft flow failures and you have no clue why, try it in the old designer and save you the hassle. Thank man, hopefully they fix this or put like a warning somewhere.

[cb23]

Hi there, I am having this issue but am using the classic designer. Do you have any suggestions for fixes in the meantime? My post is here: Re: Saving email attachment from shared mailbox - ... - Power Platform Community (microsoft.com)

[AmieRobbo]

Hello
I am having the same issue, but can't find where you speak of in the trail. Can you please advise?

[Ntulikid]

Hi

I'm not sure if you have already got your solution. 

On the attachment content , instead of using the one drive connector id, use the File Content dynamic content from the Get File Using Path connector.

I hope it will work 👍

[AmieRobbo]

Morning,

I have done as said but still the same issue

[Ntulikid]

Hi 

You need to add a get file using path connector to get the pdf you created (as you did with the picture). Then use it File Content dynamic content on the attachment content. 

[AmieRobbo]

Where abouts do I put this in the flow? does this look right. The file path isn't working but unsure what to put here either?

[Ntulikid]

I have tried to make an example for your scenario. 

After converting the file to pdf, use the SharePoint create file connector instead of the one drive Create File connector. when you get file using path makes sure the file path is similar to that on the create file and also the dynamic variable for the file name is the same. 

[AmieRobbo]

IT WORKED!! thankyou

[Ntulikid]

You are welcome!! 👍