All versions since release
The templating engine fails to correctly interpret complex expressions such as this one:
"targetElements": "${foreach(foreach(indicesAndValues(LineItems), x, concat('cardContent', x.index)), y, json(concat('{ \"elementId\": \"', y, '\", \"isVisible\": true }')))}"
The reason for this is the code mistakenly interprets the } character after \"isVisible\": true as being the end marker for the expression when it is actually a character within a string within the expression.
please review this issue for target Milestone, Inconsistencies & Priority upon triage.
Hi @dclaux. We have acknowledged this issue report. Please continue to follow this issue for updates/progress/questions.
@dclaux / @jwoo-msft / @RebeccaAnne this is currently in 20.11; Based on @dclaux 's offline update this looks to be in the works for 20.10 potentially - somethings to consider before actually considering it for 20.10 though:
Reopening until the bug is fixed in .NET as well.
Hi @dclaux. We have acknowledged this issue report. Please continue to follow this issue for updates/progress/questions.
:tada:This issue is now fixed by #4971 and successfully released as part of our [email protected] offering.:tada:
Handy links:
@dclaux FYI... You can simplify your expression:
"targetElements": "${foreach(foreach(indicesAndValues(LineItems), x, concat('cardContent', x.index)), y, {elementId: y, isVisible: true})))}"
That's the same thing as using json() to parse a JSON based string but way easier to write :)
@jwoo-msft i've moved this out to 20.12 for now but do you have cycles to look into this in 20.11? @RebeccaAnne for FYI in case you are able to load balance if the Approvals team comes back wtih requests to accelerate this delivery in .NET
Most helpful comment
@dclaux FYI... You can simplify your expression:
That's the same thing as using
json()to parse a JSON based string but way easier to write :)