Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
We have a group of dataflows that we built almost two years ago and I'm pretty sure that no one is consuming this content. I'd like to remove them, but I need to reassure the administrators that this would have zero impact.
is there any way to monitor/discover if a dataflow is being consumed by another report?
Solved! Go to Solution.
Hi,
You can use data flow metrics.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks,
Shanthakumar.
Hi,
You can use data flow metrics.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks,
Shanthakumar.
Hi @RBunting ,
Yes, you can use the lineage view function. You can see the lineage relationship between all projects in the workspace and all their external dependencies. It shows the connections between all workspace items, including connections to dataflows (upstream and downstream).
The prerequisite is that a pro account or a user with access rights to the workspace is required.
related document link: Data lineage - Power BI | Microsoft Docs
If there is still confusion, let me know immediately. Llooking forward to your reply.
Best Regards,
Henry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I don't believe downstream dataflows consuming from the target dataflow outside of the current Workspace will be shown.
EDIT: yes, this is in the documentation too "Currently, the lineage view scope for dataflows is limited to what exists in the current workspace."
The Linage View won't show you all dataflows that may be consuming from the target dataflow.
In the past I've found dataflows that had an upstream dataflow deleted would become corrupted and uneditable. I would have to delete and recreate the dataflow downstream of the deleted one, which would get a new GUID and impact consumers downstream of that. It's possible this issue has been fixed.
After getting burnt a couple times, I no longer delete dataflows, just rename with prefix "zzOld_2021-06-16_".
I just tested this, and deleting upstream dataflows no longer corrupts downstream dataflows consuming from them--less risk in deleting now.
Hi @RBunting
In here you should get the answer
Regards
Amine Jerbi
If I answered your question, please mark this thread as accepted
and you can follow me on
My Website, LinkedIn and Facebook
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.