Power Platform Community Forum Thread Details

Hello everyone,

I currently have a script that converts an Excel file to a Base64 string and sends it to SharePoint via HTTP received trigger. The trigger is successful and the value is parsed correctly.

However, when using Base64tobinary and Create File, the resulting file is corrupt. Examining the input I can see that /n is being added to the file content string. For example:

{

"$content-type": "application/octet-stream",

"$content": "UEsDBBQABgAIAAAAIQA0fpDGiQEAAC4GAAATAAgCW0NvbnRlbnRfVHlwZXNdLnhtbCCiBAIo\noAAC"

}

I'm no sure if that is the issue or just a quirk of how things are displayed in Run History. If I write the value received to a txt file in sharepoint, and then convert the contents of the text file from base 64 using python, the generated Excel file opens just fine.

Any suggestions?

Categories:

Building flows