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 / Designer gives invalid...
Power Automate
Unanswered

Designer gives invalid expression(s) error on accessing some dynamic content in the flow

(0) ShareShare
ReportReport
Posted on by 6
The flow gives only this vague error:
The input parameter(s) of operation 'Compose' contains invalid expression(s). Fix invalid expression(s) for the input parameter(s) of operation 'Compose'.
 
One of the values used is: 
body('Parse_JSON')?['productOfferingQualificationItem'][0]?['product']?['place'][0]?['id']
 
This comes while trying to access some of the dynamic content values from a previous Parse JSON action in a compose action.
Observations:
1. The flow runs fine when accessing the value in a separate compose action using above expression. There it shows the value in output.
2. The same expression when added into the Required compose action where the entire json payload is present, then it gives the error mentioned above with no other changes done.
3. Some dynamic content items are accessed successfully in the flow run but others give this error.
4. The dynamic value interactive box for the added value/expression change from 'output...' how it is visible while adding it in the code to the value it holds in the interactive box.
Although this itself hasn't caused any issue in the flow. 
5. In old designer view the same issue gives following error:
Request to XRM API failed with error: 'Message: Flow client error returned with status code "BadRequest" and details "{"error":{"code":"TemplateValidationError","message":"The power flow's logic app flow template was invalid. Unable to parse template language expression 'type': expected token 'LeftParenthesis' and actual 'EndOfData'."}}". Code: 0x80060467 InnerError: '.
 
Also, while using the same expression(above) in the json payload which is also used in a separate compose, sometimes it just gives this:
Something went wrong. Please refresh the page or try again after some time.
 
Screenshots attached. 
Screenshot 2025-11-24 120030.png
Screenshot 2025-11-24 121658.png
Categories:
I have the same question (0)
  • Power Platform 1919 Profile Picture
    2,217 Super User 2026 Season 1 on at
    The expression is correct but the error message is stating about something else (it is about type property is wrongly configured).
     
    From the images shared, compose action has "@@type" in multiple places (which is not allowed in power automate ).
    As the key for json object would become 
    @@type instead of '@@type' (which power automate doesn't allow)
     
    You should try as "'@@type'" (quote the @@type then double quote it).
    It will resolve the error 
  • Power Platform 1919 Profile Picture
    2,217 Super User 2026 Season 1 on at
    Just to add here, when ever using special characters in json keys always quote it than again double quote it, then power automate will escape the special character safely with out throwing any error.
     
    Eg : "'@odata.id'"
  • Chriddle Profile Picture
    8,686 Super User 2026 Season 1 on at
    From the images shared, compose action has "@@type" in multiple places (which is not allowed in power automate ).
    As the key for json object would become 
    @@type instead of '@@type' (which power automate doesn't allow)
    Sorry @Power Platform 1919, that is not correct,
    @@ is the correct encoding of the @ char, that otherwise indicates the start of an expression:
     

    This changes the property name to '@type' (with the extra quotes).

     
    The correct way: Encode the @ with a second one:
     
     
    Unfortunately, after a page reload, this is only displayed with one @ char in the UI, but it is still correct.
    In doubt check with "Peek code" that there are two in the connector's JSON:
     
     
    Perhaps a look at the entire JSON of the connector will help to find the problem.
  • Power Platform 1919 Profile Picture
    2,217 Super User 2026 Season 1 on at
    Hi ,
    Thanks for pointing it out, i didnt know about encode @ with another @ method,
    but when i previously had this problem in different use case (was building sharepoint rest api call), i just had to encode the json key with quotes, which solved the issue. (as mentioned in second response)
     
    sample example:
     
     
  • Chriddle Profile Picture
    8,686 Super User 2026 Season 1 on at
    Whenever you create a JSON within a Compose, encode @ with @@ (unless it is meant to be an indicator of an expression)
    This works fine:

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the April Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Vish WR Profile Picture

Vish WR 801

#2
Valantis Profile Picture

Valantis 602

#3
Haque Profile Picture

Haque 581

Last 30 days Overall leaderboard