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.
Hi mattbenj
Per my understanding, In Fabric, the Lineage view merges items into a single node only when it is 100% certain they represent the exact same logical entity.
It would otherwise splits nodes when there is a mismatch in how the connections are defined.
therefore the possible cause of this issue is Connection Mismatch. I am guessing here Your nodes are likely split because of either of the following reasons:
1. Different Connectors used in dataflows. e.g. One Dataflow might use the native Fabric Lakehouse connector, while another uses the SQL Connection String.
2. Staging Differences: If "Enable Staging" is turned on for some Dataflows but off for others, Fabric treats the data paths as distinct architectures.
3. Auth Methods: Using an Organizational Account in one and a Service Principal in another can cause a split.
possible option to fix it: i.e.to get the single-node look from your first screenshot:
1. Standardize the Destination: Open your Dataflows and ensure the Data Destination is selected via the Navigator (choosing the workspace/item from the list) rather than pasting a URL.
2. Match Staging Settings: Ensure all Dataflows writing to that Warehouse have the same "Enable Staging" toggle setting.
Hope this helps!