Forum Discussion
Understanding Lineage View
Hi mattbenj
Thank you for contacting the Microsoft Fabric community forum.
Fabric lineage is shown at the artifact level, so Lakehouse and Warehouse appear as separate nodes even when they share the same data in OneLake. When Dataflow Gen2 reads from a Lakehouse and writes to a Warehouse, lineage represents this as two distinct steps to reflect data movement between different item types.
Here is the reference:Lineage in Fabric - Microsoft Fabric | Microsoft Learn
A Lakehouse also includes a SQL analytics endpoint, which can appear as an additional node and sometimes cause confusion. Multiple nodes for what appears to be the same source or destination typically occur when different connection methods are used (such as Lakehouse connectors, SQL endpoints, or Warehouse connections), when lineage is viewed at different levels, or when similarly named items exist in different workspaces.
Better Together - the Lakehouse and Warehouse - Microsoft Fabric | Microsoft Learn
Currently, there is no supported way to merge Lakehouse and Warehouse into a single node in lineage. To maintain a clear and consistent lineage view, all dataflows should use a consistent connection approach and reference the exact same Lakehouse and Warehouse artifacts.
If you have any further questions, feel free to reach out and we’ll be glad to assist. If I’ve misunderstood any part of your scenario, please let me know.Regards,
Microsoft Fabric Community Support Team.
v-karpurapud I think there is a bit of a misunderstanding. I don't expect a Lakehouse and Warehouse to appear as one node. In this screenshot you see 3 Dataflow Gen2s. Each one reads data from a different table from the same Lakehouse (StagingLakehouse) amd writes data to three different tables in the same Warehouse (fabric_finance). I was trying to understand if there is a way to get the lineage view to show something like this.
This works like I expected for some of my other Dataflows that write to the Lakehouse.
Hi mattbenj
Thank you for clarifying. The scenario you described, where a single Lakehouse feeds multiple Dataflow Gen2s that merge into one Warehouse node, is a valid expectation, and lineage will show this when multiple dataflows write to a Lakehouse.
However, for Warehouse destinations, Fabric lineage treats each Dataflow Gen2 load as a separate event. Even if all dataflows read from the same Lakehouse and write to different tables in one Warehouse, the lineage view displays separate paths instead of combining them into a single Warehouse node.
This is the current expected behavior and reflects how Warehouse loads are modeled in Fabric lineage, not differences in connection or configuration. Currently, there is no supported way to visually combine multiple Dataflow Gen2 to Warehouse paths into one Warehouse node.
Let us know if you require any additional assistance or clarification.
Regards,
Microsoft Fabric Community Support Team.