Skip to main content
Community Hub

How Tableau lineage works

TL;DR

Understand how Atlan builds lineage for Tableau assets, the default traversal path, why Workbooks aren't in lineage by default, and how to include them.

Your AI can read this via Docs MCPcurl -fsSL "https://docs.atlan.com/install-docs-mcp" | bashConnect

Atlan builds lineage for Tableau assets by tracing how data flows from upstream database tables through Datasources, Worksheets, and Dashboards. This page explains the default lineage model, how column-level lineage (CLL) traces individual fields, and how to include Workbooks in lineage.

How lineage paths work​

By default, Atlan traces data from upstream database tables through published or embedded Datasources, then through the Worksheets that consume those Datasources, and finally to the Dashboards that contain those Worksheets.

The asset-level lineage follows these relationships:

FromTo
DatasourceWorksheet
DatasourceDashboard
  • Datasources are the entry point: Atlan resolves lineage from upstream database tables into published or embedded Datasources, which become the starting node for Tableau lineage.
  • Worksheets consume Datasources: each Worksheet that reads from a Datasource is linked downstream of it.
  • Dashboards contain Worksheets: Dashboards appear downstream of the Datasources whose Worksheets they include.
  • Worksheets must be crawled for complete lineage: lineage to Dashboards may appear incomplete or missing if the underlying Worksheets aren't crawled.

How column-level lineage works​

Column-level lineage (CLL) traces individual fields through the Tableau asset hierarchy, so you can follow a single column from a Datasource field into the calculated fields and downstream assets that depend on it.

FromTo
Datasource fieldCalculated field
Datasource fieldDatasource field
WorksheetDashboard
info

Tableau assets that haven't been refreshed since May 27, 2025 won't display column-level lineage or updated lineage paths. Re-crawl these assets to populate field-level lineage.

Why workbooks aren't in lineage by default​

Before the introduction of CLL, Atlan included Workbook nodes in the lineage graph as intermediate steps. Following the introduction of CLL and a corresponding cleanup that shipped on May 5, 2025, Workbooks were removed from lineage traversal and exports.

Workbooks are organizational containers in Tableau. They group Worksheets and Dashboards, but data doesn't flow through them directly. The actual data path is always Datasource to Worksheet or Datasource to Dashboard, so Atlan keeps Workbooks out of lineage by default.

  • Workbooks always exist as assets: they're crawled and remain available in Atlan.
  • Workbooks always appear outside lineage: you can find them in asset search, metadata views, and hierarchy navigation.
  • Workbooks appear in lineage only when you include them: by default, they're excluded from both lineage traversal and lineage exports.

If you previously saw Workbooks in lineage or lineage exports and no longer see them, this is expected behavior after the May 5, 2025 update. To show them again, include Workbooks in lineage.

Include workbooks in lineage​

To show Workbooks in lineage, set Include Workbooks in Lineage to Yes on the Advanced page of your Tableau crawler. The change takes effect on the next crawl. This option is available from Tableau app version 2.2.0.

When the option is on, Atlan links each Workbook to the assets around it. The Workbook path runs alongside the default path and doesn't replace it.

The option adds the following asset-level lineage:

FromToWhich assets
DatasourceWorkbookThe embedded Datasources in the Workbook. Published Datasources reach the Workbook through the embedded Datasource that uses them.
WorkbookWorksheetEvery Worksheet in the Workbook.
WorkbookDashboardOnly Dashboards that no crawled Worksheet feeds, such as text or image Dashboards. Atlan reaches every other Dashboard through its Worksheets.

Keep the following in mind when the option is on:

  • Column-level lineage doesn't change: fields flow from Datasource fields to Worksheet fields directly. In column-level lineage, the Workbook appears dimmed.
  • Impact analysis includes sibling assets: downstream asset lineage from a Datasource passes through the Workbook. It lists every Worksheet and Dashboard in that Workbook, including ones that don't use the Datasource. Use column-level lineage to see which assets use a specific field.
  • Some Dashboards have two paths: when Crawl Unpublished Worksheets and Dashboards is set to No, a Dashboard built only from hidden Worksheets links to its Datasource both directly and through its Workbook.
  • Turning the option off removes Workbook lineage: on the next crawl, Atlan removes the Workbook lineage and leaves all other lineage unchanged.

What is not supported​

Atlan doesn't support lineage for the following Tableau assets:

  • Tableau Flows
  • Tableau Metrics
  • Embedded dashboards

See also​