Showing results for 
Search instead for 
Did you mean: 
Kudo Commander
Kudo Commander

base64ToBinary() disappearing after saving the Flow

Hello Team,


I am getting base64ToBinary() disappeared after saving the flow. Is there any update on this bug yet? 

My formula: base64ToBinary(triggermultipartbody(0)['$content']) 

I am getting file content (string based) from HTTP request and my flow as follows:

My flowMy flow

The purpose of the base64ToBinary() is to convert unknown filetype(base64) to compatible file format in sharepoint(Binary)

This needs to be addressed as soon as possible and any other alternatives would be much appreciated.


Kind regards,




Kind regards,




Community Support
Community Support

Hi @Nagaviswanath,


I have made a test on my side and the issue is confirmed on my side.the expression with base64ToBinary() disappeared after saving the flow.


However, even if the expression with base64ToBinary() disappeared after saving the flow, the flow would always run with expression base64ToBinary().


So don't pay attention to the expression displayed in the flow,you could run your flow to achieve your requirement even if the expression with base64ToBinary() disappeared.


Best regards,




Hello @v-yuazh-msft


I don't think the base64ToBinary() is working as sharepoint is not recognising file type of the files which were sent through HTTP request in Flow. Sharepoint is showing these files as Unknown file format, so i believe the function is not working.


Don't you think sharepoint recognises converted Binary files from Base64 if the base64ToBinary() is actually working as you said?


Kind regards,




Frequent Visitor

I also get base64toString() disappearing - replaced with the dynamic content icon of the variable that is being processed, and i cannot re-edit the expression. It does appear to still be working but its really confusing to see.

FYI if I export this I can see it in the json:

"inputs": "\"@{variables('item_name')}\":  \"@{base64ToString(variables('item_content'))}\""

Not applicable

Hello @Nagaviswanath, did you found a solution for this problem ?

New Member

October 2019, still a feature of flow. 


I have found out that:

- The base64tostring/decodebase64 works if I save once and do not reopen the flow, ever. 

- If I encapsulate the method in something like trim(decodebase64(...)) or concat(decodebase64(...),'') the editor will not remove the method when reopening. 


Not a solution, but a workaround for plain/csv/xml files. I do not know about binary. 

New Member

I have the same issue on the latest version of D365..


It is not resolving base64tobinary after saving the function disappears..


Is there a solution to this issue? 




Helper I
Helper I

Confirming that this is still happening...

Contrary to what was mentioned above, my flow does not run without base64ToBinary. So once I close a flow, it stops working.

Helpful resources

MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

Microsoft Build 768x460.png

Microsoft Build is May 24-26. Have you registered yet?

Come together to explore latest innovations in code and application development—and gain insights from experts from around the world.

May UG Leader Call Carousel 768x460.png

What difference can a User Group make for you?

At the monthly call, connect with other leaders and find out how community makes your experience even better.

PA Survey Carousel Image.png

We want to hear from you!

If you are a small business ISV/Reseller, share your thoughts with our research team.

Top Solution Authors
Top Kudoed Authors
Users online (1,259)