web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Expressions embedded i...
Power Automate
Answered

Expressions embedded in HTML are converted to static values + disconnected from the original source

(0) ShareShare
ReportReport
Posted on by 6
I use Power Automate to create alerts for our users. These generally consist of Send an email (V2) actions where the body is made up of one or more string variables or Composes.
I use Append to string or Compose actions to create pretty HTML with my dynamic data values, like a list of summary totals. This has worked fine for months now.
Recently when opening one of these actions for editing I noticed that instead of seeing the start of the expression displayed in a cute blue or pink box (like fx formatDateTime... or Outputs) I see static integers.
These values seem to be the last calculated values from my last run of this flow.
I assumed this was a cute new feature, except that I can no longer click on these highlighted boxes and see or edit the underlying expression.
I find that once Power Automate designer converts my expressions to static result values AND if I click Save, my expressions (formulas) are completely gone.
What was once dynamic code is now completely static values.
CoPilot calls this flattening and thinks that the original expressions can be recovered by exporting the flow and examining the JSON. This is incorrect. The JSON contains the flattened result as well ( @{1531} ).
I'll attach a screenshot of a Compose action where the static values can be seen (some of my more complex expressions did not get flattened), and a mouseover of one of the flattened values to show that there is no longer an expression underlying the creation of the value.
 
This in my opinion is a major bug since it renders once dynamic flows as static, and disconnects the results from the source data.
flattening2.png
flattening issue1.png
Categories:
I have the same question (0)
  • David_MA Profile Picture
    14,956 Super User 2026 Season 1 on at
    It is hard to tell from your screen shot what it is of. But, most likely you are not putting the e-mail action into HTML code view mode. If you don't the e-mail comes through with the code rather than the values. Also, based on the screen shot, some of the expressions do not look valid. Any of the expressions that show as a number, do not appear to be value. 
     
     
    What are the actual expressions you are using. 
  • JL-10041257-0 Profile Picture
    6 on at
    The second image is of the Inputs Parameters for a Compose action.
    This is not an issue with the Send an email (V2) action. This occurs in the Compose which preceeds my Send action.  
     
    Your comment, "based on the screen shot, some of the expresssions do not look valid" is spot on and the issue.
    Each of those numeric values used to be an outputs('Compose') action from earlier in the flow.
    The Compose actions still exist but the connection between them and the HTML I am building is gone; only the last run value remains.
    So when I run the flow now these values do not get updated with my fresh data.
     
    I hope that helps to clarify.
  • Verified answer
    Ellis Karim Profile Picture
    12,163 Super User 2026 Season 1 on at
     
    Are you using the New designer? Can you recover anything from a previous flow, by looking at the Code View?
     
     
     
    @David_MA Do you think this a bug with the new designer?
     
    Ellis Karim
    Ellis Karim
    elliskarim.com  |  LinkedIn  |  Bluesky
    If this solved your issue, please mark it as ✅ Accepted Answer. If it helped, feel free to give it a 🩷 Like!
  • David_MA Profile Picture
    14,956 Super User 2026 Season 1 on at
    Okay, I think I understand now. The screen shot is a compose action. You'll then use the output of the compose action for the body of the e-mail. I don't know if this is the issue, but delete the first HTML tag <!-- Body -->.
     
    If that is not the issue, I have yet to encounter this. Although, if you are using the new designer as @Ellis Karim asked, I almost never use the new designer because of how many issues I have encountered when using it.
     
    One other suggestion, create variables for each of the expressions. Then insert the variable into the Compose action instead.
  • JL-10041257-0 Profile Picture
    6 on at
    The <!-- Body --> tag is an HTML comment, so that shouldn't be an issue.
     
    I have only been using Power Automate for about 7 months now, and assumed that the 'new' Designer was a stable product. How long has it been in production?
     
    I also run into an issue where I cannot add a Condition action to a flow; the UI simply ignore my clicks. I have to keep a test flow with an empty Condition in it; the Designer has no problem copying and pasting a Condition. Strange behavior.
     
    As far as variables, I started off using them and most of what I've read tells me to use Composes instead, for performance. So I've been switching.
     
    If the new designer is really not stable then I'll switch to the old one. Hopefully I can access all of the same features with it.
     
    Thanks

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Valantis Profile Picture

Valantis 377

#2
11manish Profile Picture

11manish 279

#3
David_MA Profile Picture

David_MA 234 Super User 2026 Season 1

Last 30 days Overall leaderboard