Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
See below, both scripts work fine in "import" modus.
The first script, using dataflowId does work in DirectQuery mode as well. The other one, using dataflowName doesn't work.
Although, it is able to load a preview in the Power Query editor, it does not retrieve data in the report.
Any help? We use dataflowName in the M-script to simplify the release across dev, test and production workspaces.
let
Source = PowerBI.Dataflows(null),
#"Workspace" = Source{[workspaceId=WorkSpaceID]}[Data],
#"Dataflow" = #"Workspace"{[dataflowId="2f23459-1964-41ab-ac67-9f4asdfdc40e"]}[Data],
Output = #"Dataflow"{[entity="Table_1"]}[Data]
in
Output
let
Source = PowerBI.Dataflows(null),
#"Workspace" = Source{[workspaceId=WorkSpaceID]}[Data],
#"Dataflow" = #"Workspace"{[dataflowName="df-dimension-x"]}[Data],
Output = #"DataflowD"{[entity="Table_1"]}[Data]
in
Output
@HuibvanZundert
What do you mean doesn't work, any error message? There is a limitation that Power Query Dataflows connector is not supported for sovereign cloud clusters (i.e. China, Germany and US Government clusters).
Paul Zheng _ Community Support Team
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 16 | |
| 12 | |
| 10 | |
| 7 | |
| 6 |