Expressions are removed on next open

[Delid4ve]

In my test scenario:

1: Create flow from powerapps

2: Initialise variable (type string, intial value ask in powerapps)

3: Data Operation Compose (Expression: Base64ToBinary(VariableOutput))

4: Save the flow and close

5: Open the flow

The Base64ToBinaryExpression has disappeared and you are left with the VariableOutput

Whilst it works on first save, you have to remember to redo the expression everytime you edit it.

[v-yuazh-msft]

Hi @ Delid4ve,

Could you please share a screenshot of the configuration of your flow?

I have made a test on my side and the issue is confirmed on my side.

The expression would be formated to dynamic content automatically in some condition when reopen the flow.

I have created a flow as below:

When save the flow and reopen it , the expression in the flow would be formated to dynamic content as screenshot below:

The expression in flow would be formated to dynamic content automatically in some condition,

However, this automatically formate wouldn't affect the normal run of the flow,and the flow could work fine as before.

The only alternative way could be save the expression in somewhere before you save the flow If you would like to use the expression in the flow.

Regards,
Alice Zhang

[Nagaviswanath]

Hello @v-yuazh-msft,

I am having the same problem but in my case it is very important to get the base64ToBinary() function work as it converts the Document before copying to sharepoint in compatible format to open the document. Please check screenshots for more reference:

Before saving the flowAfter saving and come back to check the FlowFile is getting saved in unknown format due to base64toBinary() not working

Here is my full formula: base64ToBinary(triggermultipartbody(0)['$content'])

Please let me know how to solve this issue.

Kind regards,

Naga

[robstuart]

I am having the same issue. Expressions drop out when the Flow is reopened. Has anyone found a fix for this?

[zdridos]

Same problem here !!

[AllanMac]

This is terrible we shouldn't need to change this everytime the flow is edited..  Is there a workaround for this yet??