Skip to main content
November 11, 2026
Column lineage for first_order traced from the stg_orders and customer_orders dbt models into two Looker explores and the Orders Pulse Looker dashboard
Column-level lineage no longer stops at your last dbt™ model. The Catalog now follows each column into the dashboards, charts, and syncs that read it, and back to the ingestion tool that loaded it. When you ask “which dashboards break if I drop this column?”, the lineage answers down to the field. Each field in an integration that reads a warehouse column is matched to the dbt model or source that builds the column. Paradime parses each asset’s SQL in the dialect of its own connection.
  • Open it from any asset. On the Columns tab of a BI or ingestion asset, click Lineage on a column, or click a column on any card in the Lineage tab. Integration assets show as cards with their tool’s logo, such as dashboards, worksheets, and syncs.
  • See how a column is computed. Click an edge to see the expression behind it, for example the DAX measure, the LookML dimension, or the Tableau calculation.
  • Know when it’s incomplete. Where Paradime can’t resolve a field to its columns, the lineage falls back to the asset and shows node-level fallback used.
  • Asset-level lineage too. Integration assets now have asset-level lineage in the Catalog, including the links between Looker or Tableau assets in the same tool.
  • Ask DinoAI. DinoAI agents, the copilot, the Slack agent, and MCP clients trace a dbt™ column into these tools with the Column-Level Lineage tool. Ask “Which Looker dashboards use fct_orders.revenue?” and the agent names them.
  • Bring your own tool. The Custom Integration API takes upstreamFields and downstreamFields on each field, so lineage into an in-house tool shows on the same canvas.
See Lineage into BI and ingestion tools. Shipped in Paradime v6.25.2.