Flow Creates Unreadable File in One Drive

[daveearley]

Hello,

I have created a Flow which takes an attachment from a Salesforce report email subscription and creates a copy of the file in One Drive.  When I access the file in One Drive it is either encrypted or corrupted.  To my knowledge Salesforce and Power Automate do not encrypt data by default.  

If I export the report from Salesforce to my device it displays correctly in CSV format.  If I open the CSV attachment from my email it displays correctly.  I have tried this automation from two different accounts and the file is never readable once it reaches One Drive.  What could be causing this issue?

This is how the file looks in One Drive: 

This is how the Flow is designed:  

There are active connections to the correct Outlook and One Drive accounts from the Flow.  

Parameters for trigger are: To, Include Attachments (Yes), Subject Filter, and Only With Attachments (Yes).  

Flow created the loops automatically; 'body/value' in first and 'attachments' in second.  The Create File elements are taking the same 'contentBytes' to create the same file in two different folders, and the File Names are in CSV format.  

I checked the email accounts being used to ensure encrypted content was disabled.  Thanks for any input!

[v-mengmli-msft]

Hi @daveearley ,

As far as I know, we should add "Get attachments" before create file with attachments of email.

Please try this:

Best regards,

Rimmon

[daveearley]

Thanks for the help.  When I copy your process I receive the following error:  

The file I am using from the attachment does have two rows of data, so it is not empty.  I have selected 'attachment' for the output from previous step value.  I have also selected Message Id and Attachment Id to be included in the Get Attachment element.  

Flow automatically included a For Each element prior to the Apply to Each element containing 'body/value', which I removed.  

If I create the same Flow from scratch I receive an error when trying to get the attachment, which seemed to work without the Get Attachment element before.  

[v-mengmli-msft]

Hi @daveearley ,

I recommend switching to classic mode and trying again, the new mode is sometimes unstable.

When you go into the loop after you select the attachment ID in "Get Attachment" it is due to the fact that sometimes the attachment of the email is multiple, please do not remove the "Apply to each" that appears automatically, otherwise this may cause errors in your flow.

According to my test, if we use "get attachment" to get the content of the file, the created file cannot be opened. This is due to the fact that the file content is somewhat different in "when an email arrives" and "get attachment".

Best regards,

Rimmon

[daveearley]

Thanks for the info.

I recreated the Flow yesterday using the original design.  The Flow ran successfully, and I was able to read the file properly in One Drive.  Perhaps some input, output or connection was modified, but I cannot confirm any differences.  I guess I can chalk another one up for persistence.  I'm not sure what was causing the file corruption, but this is working now.  The current design does NOT use the Get Attachment element.  Will this be an issue?  

Should I still be trying to use the Get Attachment element even though the Flow ran successfully?  

Can I have fault emails sent to a different email address in the event the Flow does not run at certain times?  

[daveearley]

I found the "attachment name" to be the cause of the file corruption.  If I use the Attachment Name input from the email, the file is successfully created in One Drive.  However, if I use a customized name for file creation, the file is not readable once created.  

Am I unable to customize the file name before it is created using this element?  I need the file name to be different than what is coming into the email, and it needs to overwrite the previous file in One Drive.  Do I need to use other components to accomplish this?  

[daveearley · Accepted solution]

The issue is now resolved.  I modified the Flow with a condition to accept emails with an attachment name ending in "csv" and included my unique file names for each file being created.  When I viewed these files in One Drive the first was correct, the second file appeared corrupted for a split second and then switched to the correct format.  Both files are now readable after being created with Flow.  Thanks for the help!  Current design is as follows:  

[v-mengmli-msft]

Hi @daveearley ,

Glad to hear that the problem has been solved!

You can accept replays you find useful as solutions. Thanks for posting here, and I hope all is well with the rest of the flow.

Best regards,

Rimmon