Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
ISSUE (gremlins are very busy today):
0__drop a Teams activity onto the design surface.
1__in Message section, type some text, then click on View in expression builder to open the pipeline expression builder.
2__at various locations of your choosing, insert some system variables by clicking on the variable names in the pane below the editor.
3__note that the '@' symbol is automatically inserted at the very start of the whole string AND NOT in front of each function call:
Hi @Element115 ,
Thanks for using Fabric Community.
At this time, we are reaching out to the internal team to get some help on this .
We will update you once we hear back from them.
Hi @Element115 ,
Currently this is an expected behaviour, we can observe the same functionality in Azure Data Factory too.
Appreciate if you could share the feedback on our feedback channel. Which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.
Hope this helps. Please let me know if you have any further queries.
I will. But how could this be expected behavior (I read this statement as this is how it was designed on purpose)? How could this be since it breaks the code? After the wrong interpolation, the editor flashes an error message. That looks more like a bug than a feature, wouldn't you say so?
Hi @Element115 ,
I appreciate for your feedback, as Team is continuously working on many areas and features, these are some minor cases needs to be handled. However once you share feedback in feedback channel, which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.
I hope this is helpful.
Thank you.
I have done so.
Why do you say this is a minor case? It results in breaking the code as evidenced by the error message produced by the Expression builder since only the '@' symbol is interpolated and none of the '{' and '}'.
Hi @Element115 ,
Thanks for your time and sharing this feedback. Lets wait for team to look into it.
Why does the admin of the Fabric Ideas forum say this?
This doesn't appear to be a feature request or idea. Please feel free to create a new idea with more information about what you'd like to accomplish and whats the gap in the current product.
What is not clear here? The string interpolation is broken. Isn't this an obvious bug? And why do you guys tell me to post such things under Fabric > Ideas and then the admin of said forum says it shouldn't be posted there!??
At this rate, we'll still be here next year waiting for a solution.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Fabric update to learn about new features.
User | Count |
---|---|
6 | |
4 | |
3 | |
3 | |
3 |