Actions to reproduce:
Create a flow with a compose step, enter a function with a nested function:
Save the Flow, then edit the flow. The Compose step strips the outer function in the display:
I'd expect the flow step to maintain the function as I entered it.
I saw this behaviour too (but attributed it to something else) as I find flows with nested functions also tend to break when looking at their history...
Have you seen that?
On further testing, my issue is related but separate. The Base64ToBinary() function is the culrpit. As soon as I use it, not only does it dissapear as per what @jakekemme reported, but while the workflow runs ok, you cannot view history 😞
I quickly wrote a test flow with a button trigger to test base64ToBinary, but cannot make history disappear, so it is probably unrelated, or indirectly related to the compose step stripping the outer function on display
I don;t want to hijack your issue... so I wont paste further here. You will see the bug I have logged and the thread... I am working from a request triggert and passing it a JPG in the body by grabbing triggermultipartbody(0)['$content']. Interesting that it worked for you though...
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Join us on June 28 for our monthly User Group leader call!
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
Are you new to designing flows? What is your biggest struggle with Power Automate Designer? Help us make it more user friendly!