Skip to main content
The list view shows the same dependencies as the graph, but as a table, which is often easier for scanning, filtering, and sharing. Switch to it with the Graph / Table toggle in the lineage bar.

​
Columns

Each row is a related asset, with:
  • Node name, with its file path underneath.
  • Direction: whether it’s upstream of, downstream of, or the current asset. While you trace a column, it can also be related (see below).
  • Node type: model, source, test, BI asset, and so on.
  • Package: the dbt™ package or project it belongs to.

​
While you trace a column

If you trace a column on the graph and then switch to Table, the table shows that trace instead of the model’s dependencies. The line above the table names what you are looking at, for example Column lineage for orders.customer_id during a trace and Model-level dependencies of orders when nothing is traced. During a trace:
  • Direction follows the column’s value path only. An asset the trace reaches any other way is related.
  • A Grain column shows how each asset is connected: column when the value flows through it, indirect when it connects only through a join, filter, or grouping key, and table when it connects only at table level, for example because part of the path could not be parsed down to columns.
  • Download CSV exports the trace, including the Grain column.
In either mode, warnings about the result, such as a fallback to table-level lineage or a depth limit that cut the graph short, appear as badges above the table.

​
Filter and export

  • Use the toolbar filters to narrow by Direction or Package.
  • Click Download CSV to export the current list, for example to share an impact analysis or attach it to a change request.
The list respects the same depth and node-type settings as the graph, and follows any column you are tracing, so narrow the graph first to get a focused export.