Forum Discussion

tarektm17's avatar
tarektm17
New Member
2 days ago
Solved

A bug in the Data pipeline expression builder

Since last week's Fabric update, the Expression Builder is generating incorrect expressions when selecting pipeline parameters. For example, instead of generating:

It writes @linkedService().<parameter_name> instead of @pipeline.parameters.<parameter_name>. 

The expression is immediately flagged with an "UnsupportedConcept" error. Additionally, the value cannot be saved even after manually correcting the expression to the proper pipeline parameter syntax. The issue occurs with both newly created and existing parameters, suggesting a regression introduced in the latest Fabric update.

 

  • Hi tarektm17​,
    Hope you are alright, the workaround for this issue would be manually entering the expression details in Fabric UI until Microsoft fabric fixes the issue.

    As an example, 

    @[email protected]<parameter_name>

    Since you mentioned that even fabric UI does not allow you to enter the details manually, so instead of using the UI interface, i would recommend that directly editing the code through original Jason code view and save the changes. 

    If this does not works then you need to open Microsoft support ticket at Microsoft Fabric Support Portal.

    If this helps, ✓ Mark as Kudos | Help Other




        





     

2 Replies

  • Hi tarektm17​,
    Hope you are alright, the workaround for this issue would be manually entering the expression details in Fabric UI until Microsoft fabric fixes the issue.

    As an example, 

    @[email protected]<parameter_name>

    Since you mentioned that even fabric UI does not allow you to enter the details manually, so instead of using the UI interface, i would recommend that directly editing the code through original Jason code view and save the changes. 

    If this does not works then you need to open Microsoft support ticket at Microsoft Fabric Support Portal.

    If this helps, ✓ Mark as Kudos | Help Other




        





     

  • Hi Murtaza_Ghafoor​ ,

    Indeed, I was deploying this workaround (using 'Edit Json') and it actually works. I raised a ticket with Microsoft and will keep this post updated.

    Thanks