Forum Discussion
BUG::PIPELINE::EXPRESSION BUILDER::INTERPOLATION
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.
- Element1152 years agoMemorable Member
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?
- Anonymous2 years agoNot applicable
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.- Element1152 years agoMemorable Member
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 '}'.