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!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
Dear Community,
I've been able to save most of my existing Dataflows as Gen 2 and use them successfully.
I have an issue with a Dataflow that is shared and used by at least 13 Semantic models in my work space and others in workspaces that I don't have visibility.
Is there any way to overwrite an existing Dataflow Gen 1 with a Gen 2 so it is later used by the existing reports?
Is therea any way to identify what reports in addition to the ones in my workspace are using the Dataflow or the Semantic model ?
Thanks
Hi @sakBI,
The @rohit1991 response is accurate, you can’t overwrite a Gen1 Dataflow with a Gen2 version, as the migration process creates a new Dataflow ID, so you’ll need to manually reconnect all related datasets and semantic models.
Additionally, To find out which reports or semantic models are linked to your Gen1 Dataflow, use the Fabric Lineage View in your workspace. For a more comprehensive check across workspaces, your Power BI Administrator can leverage the Power BI REST APIs (such as GetDatasources, GetDatasets, and GetReports) to list everything connected to the old Dataflow. It’s best to keep the Gen1 Dataflow active until all datasets and reports are updated to the Gen2 version.
Power BI REST APIs for embedded analytics and automation - Power BI REST API | Microsoft Learn
Thank you.
Hi @sakBI,
As we did not get a response, may I know if the above reply could clarify your issue, or could you please help confirm if we may help you with anything else?
Thank you.
Dear @v-sgandrathi ,
Thanks for following up , I was not able to get the clearance from my customers until Yesterday . I reminded that I had a Master report that was the one leading the semantic model and most of other reports pointed to that .
I decided to point query by query to the new Dataflow, I evaluated using parameters but as long as data remains withing Dataflow the change should be suficcient.
The main report is working but I've lost the lineage view on the portal , the Dataflow remains isolated showing no lineage but the Semantic model works , so I will need more time to review .
In any case your responses were correct and I appreciate your fast feedback .
I think this topic can be considered resolved .
Kind regards,
Hi @lluisak,
Thank you for providing the update and extra context. It's good to know that the migration and query re-mapping to the Gen2 Dataflow are functioning as expected. After switching to a new Dataflow, it's normal for lineage to look incomplete for a while because the new object has a different ID. Once all related datasets and reports refresh from the Gen2 source, the lineage view should update automatically.
You can manually refresh or re-publish the main semantic model to speed up the lineage graph update. If the view still doesn't show after verifying connections, try clearing the workspace cache or reopening the lineage view.
You can mark the helpful reply as the accepted solution so others can easily find it if they encounter a similar issue.
Thank you.
Hi @sakBI
You can’t overwrite a Gen1 Dataflow with Gen2 - migration creates a new Dataflow ID, so existing reports or semantic models won’t auto-connect.
Could you please try below steps:
Open each dataset >> Transform Data >> Data source settings >> Change source >> point to the new Gen2 dataflow.
Use Fabric Lineage view or Power BI REST API (GetDatasources, GetDatasets, GetReports) to find which reports use the old Dataflow.
If you don’t have access, ask an admin to run the API tenant-wide.
If still not work try below steps:
Export Gen1 query and recreate it in Gen2.
Reconnect datasets manually or rebuild dependent models.
Keep Gen1 active temporarily until all links are updated.
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the October 2025 Power BI update to learn about new features.