Forum Discussion
Community ChampionGen2 (CI/CD) dataflow not available in Dataflow connector
Not sure if this is going to be a Desktop issue or a Service issue:
I have created a Gen2(CI/CD) Dataflow in a Fabric-enabled workspace. However, when I try to connect to it thru Power BI Desktop, the only connector where it shows up is Power BI Dataflows (Legacy).
Dataflow connector
Power BI dataflows (Legacy)
Are there settings in the Workspace or on the Dataflow itself that I need to check/change? None of the documentation is very clear on what needs to be set up in order to consume the data in Power BI Desktop.
Thanks,
David
Hi dedelman_clng,
Thank you for reaching out to the Microsoft fabric community forum and providing the additional information. To clarify, the behavior you are experiencing is expected. The Dataflows connector is designed for Fabric Gen1 Dataflows that are not hosted on Fabric capacity. When a workspace is Fabric-enabled, both Gen1 and Gen2 Dataflows are accessed through the Power BI Dataflows (Legacy) connector. This explains why you can see certain workspaces via the Dataflows connector those not on Fabric capacity, while others including your Gen2 Datafloware only available through the Legacy connector.
No changes are required at the tenant or workspace level. This is the intended functionality based on whether the workspace is Fabric-enabled. For Gen2 Dataflows, the recommended approach is to write the output to a Lakehouse or Warehouse, then connect using a Semantic Model (Direct Lake) or import directly from the Warehouse.
Hope this helps if you have any queries we are happy to assist you further.
Regards,
Community Support Team.
3 Replies
- ToddChitt
Super User
This is as designed. The Fabric Dataflow Gen 2 is designed to write data to a destination, such as a lakehouse or warehouse. You can set it up in the lower right corner when you have it open. Then from there, build a Semantic Model to include the table(s). Connect Power BI using Direct Lake and select the Semantic Model, or hit the warehouse directly using import mode.
Hope this helps.
- dedelman_clng
Hi ToddChitt - thank you for the feedback.
I also have a Gen 1 dataflow in the same workspace, and it is not showing in the Dataflows connector either (only thru Power BI dataflows (Legacy))
In fact, as you can see, there are 6 workspaces that have dataflows (all Gen 1 except for the specific Gen 2), and only 3 of them can be seen using the Dataflows connector. Could there be a setting that I am missing, maybe at the tenant level?
(edit to add): The workspaces shown on the Dataflows connector (L) are not on Fabric capacity.
Thanks
David
Hi dedelman_clng,
Thank you for reaching out to the Microsoft fabric community forum and providing the additional information. To clarify, the behavior you are experiencing is expected. The Dataflows connector is designed for Fabric Gen1 Dataflows that are not hosted on Fabric capacity. When a workspace is Fabric-enabled, both Gen1 and Gen2 Dataflows are accessed through the Power BI Dataflows (Legacy) connector. This explains why you can see certain workspaces via the Dataflows connector those not on Fabric capacity, while others including your Gen2 Datafloware only available through the Legacy connector.
No changes are required at the tenant or workspace level. This is the intended functionality based on whether the workspace is Fabric-enabled. For Gen2 Dataflows, the recommended approach is to write the output to a Lakehouse or Warehouse, then connect using a Semantic Model (Direct Lake) or import directly from the Warehouse.
Hope this helps if you have any queries we are happy to assist you further.
Regards,
Community Support Team.
