I have a flow where some early steps perform string operations:
I later use the substring output in an email message. It shows as
and it works fine when I save and test my flow. It will continue working fine for all flow runs until I ever click "Edit" on this flow again. As soon as it opens for editing, the email message shows this field as:
"Body" instead of "Output". If I save it after it's transformed itself, the flow will fail until I delete it from the email and insert it again using the Dynamic content list to choose the "Substring" step.
In short: it works when first inserted and saved, but if you edit the Flow later it changes (even if you don't open/look at that code, just opening the flow for editing causes it to change).
Can you guide me a little more on that usage? I thought I could give it a go but I must be doing it wrong.
I added a compose step immediately after my substring step, using the output of the substring as the input for Compose.
But when I go to the later step to edit the email body, "compose" isn't in the list of available fields to add into the email text.
Here's a screen snip so far:
Check out the News & Announcements to learn more.
Participate in the Power Virtual Agents Community Challenge
Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.
DynamicsCon is a FREE, 4 half-day virtual learning experience for 11,000+ Microsoft Business Application users and professionals.