> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trydatawise.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Lineage

Datawise builds end-to-end lineage from your warehouse through dbt to your BI layer. When a schema change is detected, the lineage graph shows you exactly what's at risk, from the source table to the Tableau workbook a stakeholder opens Monday morning.

## What Lineage Covers

```
Snowflake / BigQuery / Postgres
        ↓
    dbt models
        ↓
Tableau workbooks / Power BI reports
```

Each layer is connected based on actual dependencies: which dbt models `ref()` or `source()` which warehouse tables, and which BI assets consume which dbt models or warehouse tables directly.

## Table Lineage vs Column Lineage

|                                 | Availability            |
| ------------------------------- | ----------------------- |
| Table lineage (Stack Lineage)   | All plans               |
| Column lineage (Column Lineage) | Pro and Enterprise only |

Column lineage traces specific fields end-to-end. For example: if `revenue` in a Tableau workbook is derived from `order_amount` in a warehouse table, column lineage shows that connection explicitly.

## Viewing the Lineage Graph

Go to **Lineage** in the left navigation. Nodes are assets. Edges are dependencies.

* **Pan** — click and drag on the canvas.
* **Zoom** — scroll to zoom in or out.
* **Minimap** — bottom-right corner for orientation in large graphs.
* **Fullscreen** — expand to your full browser window.
* **Search** — find a specific asset by name. The graph recenters and highlights direct connections.

## Breaking Change View

From any Schema Radar detection, click **View in Lineage** to open the graph scoped to that change.

In breaking change mode:

* The changed asset is centered.
* Downstream risk edges are highlighted in red.
* Assets with no lineage path to the changed asset are dimmed.

## Lineage Accuracy

| Condition                                   | Result                                                             |
| ------------------------------------------- | ------------------------------------------------------------------ |
| Snowflake or BigQuery + dbt Cloud connected | Warehouse-to-model lineage fully resolved.                         |
| Tableau or Power BI connected               | Model-to-BI lineage resolved for assets with extractable metadata. |
| dbt `source()` definitions present          | Source-to-model edges resolved.                                    |
| dbt `ref()` used between models             | Model-to-model edges resolved.                                     |
| Direct SQL in BI tool                       | BI asset may not resolve to a specific warehouse table.            |

If a connection can't be resolved, the edge is omitted rather than shown incorrectly.

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="Why is a Tableau workbook missing from the lineage graph?">
    The workbook may not have a resolvable data source connection. This can happen if it connects via custom SQL. Check that the Tableau connector has finished ingestion and the workbook is in a project Datawise has access to.
  </Accordion>

  <Accordion title="Does lineage update in real time?">
    No. Lineage updates on each ingestion run. Trigger a manual sync from the Connectors page to update the graph after adding new assets.
  </Accordion>
</AccordionGroup>