Forum Discussion
"Keyword not supported: variables" error using Dataflow gen2 when evaluating Fabric.Warehouse()
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.
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
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.