Forum Discussion

JuanFcoCalquin's avatar
JuanFcoCalquin
Frequent Visitor
2 months ago
Solved

"Keyword not supported: variables" error using Dataflow gen2 when evaluating Fabric.Warehouse()

Dataflow Gen2 fails in Power Query editor when evaluating Fabric.Warehouse() navigation query.

The issue occurs before refresh execution, while editing/evaluating standard M steps. It also occurs with a basic Dataflow Gen2 using Enter Data as source and Fabric Warehouse as destination.

Error:
Keyword not supported: variables.
Parameter name: keyword.

Environment:
Fabric capacity: F8
Client version: 2606.1.29545-train

 

  • v-anbandari's avatar
    v-anbandari
    2 months ago

    Hi JuanFcoCalquin ,

    Thank you for the detailed update.

    Based on your findings, the issue appears to be specific to the Dataflow Gen2 scenario using a gateway-based connection, as the gateway and Fabric Warehouse both work correctly in other scenarios.

    Please consider the following points:

    • Create a new Dataflow Gen2 instead of reusing the existing one.

    • Test the same configuration in a new workspace.

    • Recreate the gateway connection and reselect it during Dataflow configuration.

    • Remove and re-add the Warehouse destination to refresh the destination metadata.

    Thank you for sharing these findings. They help narrow down the scope of the issue and may be useful to others experiencing similar behavior.

5 Replies

  • v-anbandari's avatar
    v-anbandari
    Community Support

    Hi JuanFcoCalquin,
    Thank you for reaching out to the Microsoft Fabric Community.

    Based on the error details shared, the failure is occurring while Dataflow Gen2 is evaluating the Fabric.Warehouse() navigation query. Since the same behavior can be reproduced with a simple Enter Data → Fabric Warehouse scenario,the issue does not appear to be related to the query transformations.

    As a troubleshooting step, you can try the following points:

    • Recreate the Fabric Warehouse connection and verify that the connection is configured correctly.
    • Remove and re-add the Warehouse destination in Dataflow Gen2 to refresh the destination metadata.
    • Review the Microsoft documentation to ensure the Warehouse connection and destination settings are configured according to the documented requirements.

    Relevant Microsoft documentation:

    Thank you.

  • Hi v-anbandari , thanks for your reply

    We think it's a problem with the data gateway, because we have now confirmed the following:

    1. The on-premises gateway works correctly outside Dataflow Gen2:
    A Power BI semantic model connected directly to SQL Server refreshes successfully through the same gateway.

    2. Fabric Warehouse works correctly outside the gateway path:
    A clean Dataflow Gen2 using Enter Data and a cloud connection writes successfully to the Warehouse.

    3. The failure is triggered specifically when Dataflow Gen2 attempts to use a gateway-based connection in the Warehouse/Dataflow path.

    4. After this gateway-based attempt, the Dataflow/connection metadata appears to remain in a corrupted state:
    even when switching back to a non-gateway/cloud connection, the same error persists.

    This strongly suggests a Dataflow Gen2 / Fabric Warehouse / Gateway binding metadata issue, where an unsupported “variables” keyword is being persisted or passed to the gateway connection string parser.

    I hope this extra information helps you help us with the problem

    • v-anbandari's avatar
      v-anbandari
      Community Support

      Hi JuanFcoCalquin ,

      Thank you for the detailed update.

      Based on your findings, the issue appears to be specific to the Dataflow Gen2 scenario using a gateway-based connection, as the gateway and Fabric Warehouse both work correctly in other scenarios.

      Please consider the following points:

      • Create a new Dataflow Gen2 instead of reusing the existing one.

      • Test the same configuration in a new workspace.

      • Recreate the gateway connection and reselect it during Dataflow configuration.

      • Remove and re-add the Warehouse destination to refresh the destination metadata.

      Thank you for sharing these findings. They help narrow down the scope of the issue and may be useful to others experiencing similar behavior.

  • v-anbandari's avatar
    v-anbandari
    Community Support

    Hi JuanFcoCalquin ,
      

    Could you please confirm if your issue has been resolved using the suggested approach? This will help other community members facing similar scenarios.
     

    Thank you for being part of the Microsoft Fabric Community.

    • JuanFcoCalquin's avatar
      JuanFcoCalquin
      Frequent Visitor

      Hi v-anbandari 

      Yes, the suggested steps were helpful and led us to the solution.
      Thank you for your support.


      Juan Francisco Calquín M.