> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.1/connectors/connector-repositories/reporting-tool/tableau/tableau-lineage.md).

# Tableau - Lineage

This article outlines the lineage coverage, configuration requirements, supported components, transformation support, supported use cases, partial or limited coverage, unsupported scenarios, and current functional status for lineage extraction in Tableau.

The Tableau connector provides automated lineage extraction across Tableau Workbooks, Dashboards, Worksheets, Datasources, and source systems. It provides end-to-end visibility from source tables, files, and SQL queries through Tableau Datasources and Workbooks to Worksheets, Dashboards, and other visualizations. The connector also supports column-level lineage and calculated-field lineage to provide visibility into data flow and supported transformations.

## Lineage Configuration Requirements

Successful lineage extraction depends on access to Tableau Workbook metadata and the availability of source metadata in OvalEdge. The following requirements apply to Tableau lineage extraction.

### Configuration Requirements Table

<table><thead><tr><th width="221">Configuration</th><th>Required Detail</th></tr></thead><tbody><tr><td>Tableau Workbook XML</td><td>Access to Tableau Workbook XML files stored in the <code>SourceCode</code> table is required for lineage extraction.</td></tr><tr><td>Source Database Metadata</td><td>Source databases must be crawled in OvalEdge before lineage is built so that source tables and columns can be matched with Tableau metadata.</td></tr><tr><td>Source Column Metadata</td><td>Source table and column metadata must be available for column-level lineage and source-to-target matching.</td></tr><tr><td>SQL Metadata</td><td>SQL definitions available in Tableau Workbook metadata must be accessible for SQL parsing and lineage mapping.</td></tr><tr><td>File Datasource Metadata</td><td>Excel and CSV datasource metadata must be available for file-to-worksheet lineage where applicable.</td></tr></tbody></table>

{% hint style="info" %}
Missing Tableau Workbook XML, unavailable source metadata, or incomplete source table and column metadata may result in incomplete lineage generation or unresolved source-to-Tableau relationships.
{% endhint %}

### Lineage Components

The following table identifies the Tableau components and lineage features supported by the connector.

<table data-search="false"><thead><tr><th>Component / Feature</th><th align="center">Supported</th></tr></thead><tbody><tr><td>Workbooks</td><td align="center">✅</td></tr><tr><td>Dashboards</td><td align="center">✅</td></tr><tr><td>Worksheets / Views</td><td align="center">✅</td></tr><tr><td>Datasources</td><td align="center">✅</td></tr><tr><td>Direct Table Connections</td><td align="center">✅</td></tr><tr><td>Custom SQL Queries</td><td align="center">✅</td></tr><tr><td>Calculated Fields</td><td align="center">✅</td></tr><tr><td>Nested Calculations</td><td align="center">✅</td></tr><tr><td>File Datasources (Excel/CSV)</td><td align="center">✅</td></tr><tr><td>Columns (Direct Mapping)</td><td align="center">✅</td></tr><tr><td>Column Metadata Mapping</td><td align="center">✅</td></tr><tr><td>Story Points</td><td align="center">✅</td></tr><tr><td>Chart-to-Chart Lineage</td><td align="center">✅</td></tr><tr><td>Table-to-Chart Lineage</td><td align="center">✅</td></tr><tr><td>Column-to-Column Lineage</td><td align="center">✅</td></tr><tr><td>File-to-Chart Lineage</td><td align="center">✅</td></tr><tr><td>Multi-Connection Filtering</td><td align="center">✅</td></tr><tr><td>Hyper Datasources</td><td align="center">⚠️</td></tr><tr><td>SQL Proxy Connections</td><td align="center">⚠️</td></tr><tr><td>Parameters</td><td align="center">⚠️</td></tr><tr><td>Context Filters</td><td align="center">⚠️</td></tr><tr><td>Level of Detail (LOD) Expressions</td><td align="center">⚠️</td></tr><tr><td>Relationships</td><td align="center">⚠️</td></tr><tr><td>Hierarchies</td><td align="center">⚠️</td></tr><tr><td>Extract Datasources</td><td align="center">❌</td></tr></tbody></table>

{% hint style="info" %}
The ⚠️ icon indicates partially supported functionality where lineage coverage depends on metadata availability, calculation complexity, connection configuration, or the specific Tableau implementation.
{% endhint %}

## Column Creation Support

This section outlines lineage support for columns created through expressions, aggregations, calculated fields, renamed columns, SQL queries, and metadata mappings.

### Column Creation from Lineage

<table data-search="false"><thead><tr><th>Transformation Type</th><th align="center">Supported</th></tr></thead><tbody><tr><td>Expressions</td><td align="center">✅</td></tr><tr><td>Aggregations</td><td align="center">✅</td></tr><tr><td>Calculated Fields</td><td align="center">✅</td></tr><tr><td>Renamed Columns</td><td align="center">✅</td></tr><tr><td>Temp Columns (from SQL Queries)</td><td align="center">✅</td></tr><tr><td>Semantic Columns (Metadata Mapped)</td><td align="center">✅</td></tr><tr><td>Parameter-Driven Columns</td><td align="center">⚠️</td></tr><tr><td>Extract Columns</td><td align="center">❌</td></tr></tbody></table>

{% hint style="info" %}
The ⚠️ icon indicates partial lineage coverage for parameter-driven columns. The resulting lineage depends on the availability of parameter and transformation metadata.
{% endhint %}

## Supported Use Cases

The Tableau connector supports lineage extraction across Tableau Workbooks, Dashboards, Worksheets, Datasources, source tables, SQL queries, and supported file datasources.

### Supported Lineage Scenarios

<table data-search="false"><thead><tr><th width="261">Supported Scenario</th><th>Details</th></tr></thead><tbody><tr><td>Dashboard → Worksheet Lineage</td><td>Lineage between Tableau Dashboards and associated Worksheets or Views.</td></tr><tr><td>Chart → ChartChild Lineage</td><td>Lineage across Dashboard and Worksheet child relationships represented through the Tableau reporting hierarchy.</td></tr><tr><td>Datasource Table → Worksheet Lineage</td><td>Lineage from source tables referenced by Tableau Datasources to Worksheets.</td></tr><tr><td>Datasource → Dashboard Lineage</td><td>Lineage from Tableau Datasources through Worksheets to Dashboards.</td></tr><tr><td>Workbook SQL Lineage</td><td>SQL parsing and mapping from SQL definitions available in Tableau Workbook metadata.</td></tr><tr><td>Extract / Published Datasource → Workbook Lineage</td><td>Lineage from supported Extract or Published Datasource references to Tableau Workbooks where the required metadata is available.</td></tr><tr><td>CSV / Excel File → Worksheet Lineage</td><td>Lineage from supported CSV and Excel file datasources to Tableau Worksheets.</td></tr><tr><td>Column Rename Lineage</td><td>Lineage for columns that are renamed within supported Tableau transformations.</td></tr><tr><td>Column Calculation Lineage</td><td>Lineage for calculated columns and supported calculation expressions.</td></tr><tr><td>Column Aggregation Lineage</td><td>Lineage for supported aggregation transformations.</td></tr><tr><td>Datasource Field → Worksheet Field Lineage</td><td>Column-level lineage from Tableau Datasource fields to corresponding Worksheet fields.</td></tr><tr><td>Table-to-Chart Lineage</td><td>Lineage from source tables to Tableau charts or visualizations.</td></tr><tr><td>Column-to-Column Lineage</td><td>Lineage between source columns and corresponding Tableau fields.</td></tr><tr><td>File-to-Chart Lineage</td><td>Lineage from supported Excel and CSV file sources through Tableau objects to charts.</td></tr></tbody></table>

{% hint style="info" %}
Lineage extraction depends on Tableau Workbook XML metadata, available source metadata, SQL parsing, and the ability to match Tableau fields with crawled source tables and columns.
{% endhint %}

## Partial or Limited Coverage

Certain Tableau scenarios provide partial lineage coverage because calculation complexity, runtime parameters, multiple source relationships, or datasource metadata can limit the ability to resolve complete lineage.

### Scenarios

<table data-search="false"><thead><tr><th width="192">Scenario</th><th width="332">Limitation Description</th><th width="298">Recommendation / Workaround</th></tr></thead><tbody><tr><td>Complex Calculated Fields</td><td>Complex or nested calculations, particularly calculations that use LOD expressions, may not fully resolve into individual lineage relationships.</td><td>Validate lineage manually for complex calculated fields where detailed transformation-level lineage is required.</td></tr><tr><td>Aggregations</td><td>Functions such as <code>SUM</code>, <code>COUNT</code>, and <code>AVG</code> may not always be captured as distinct transformation steps in the lineage flow.</td><td>Validate aggregation logic manually where expression-level lineage is required.</td></tr><tr><td>Blended Data Sources</td><td>Lineage visibility is limited across multiple joined or blended data sources.</td><td>Validate relationships across blended sources manually where required.</td></tr><tr><td>Dynamic Parameters</td><td>Parameter-driven filters and calculations may not be fully resolved during lineage extraction.</td><td>Validate parameter-dependent lineage manually where required.</td></tr><tr><td>Custom SQL</td><td>Complex or multi-query Custom SQL statements may provide partial parsing and lineage mapping.</td><td>Use supported SQL structures where possible and validate complex SQL lineage manually.</td></tr><tr><td>Published Datasources</td><td>Backtracking from Published Datasources to the original physical data sources may be limited.</td><td>Validate physical source dependencies separately where complete backtracking is required.</td></tr><tr><td>Extract Connections</td><td>Incremental refresh lineage may not appear in the resulting lineage relationships.</td><td>Validate extract refresh dependencies separately where required.</td></tr><tr><td>Derived Worksheets or Dashboards</td><td>Dataset lineage status may indicate incomplete lineage for Worksheets or Dashboards derived from complex datasource relationships.</td><td>Review affected lineage paths and validate derived dependencies manually.</td></tr><tr><td>Hyper Datasources</td><td>Lineage coverage is partial for Hyper Datasources.</td><td>Validate Hyper datasource dependencies manually where complete lineage is required.</td></tr><tr><td>SQL Proxy Connections</td><td>Lineage resolution may be limited for SQL Proxy Connections.</td><td>Ensure the required source metadata is available and validate affected lineage paths manually.</td></tr><tr><td>Context Filters</td><td>Context filter dependencies may not be fully represented in lineage.</td><td>Validate filter dependencies separately where required.</td></tr><tr><td>Relationships</td><td>Tableau relationships may not provide complete relationship-level lineage coverage.</td><td>Validate source relationships manually where detailed relationship lineage is required.</td></tr><tr><td>Hierarchies</td><td>Hierarchy dependencies may not be fully represented in lineage.</td><td>Validate hierarchy relationships separately where required.</td></tr></tbody></table>

{% hint style="warning" %}
Complex calculations, LOD expressions, dynamic parameters, blended data sources, complex Custom SQL, Published Datasources, Extract Connections, and incomplete source metadata may reduce lineage completeness and column-level accuracy.
{% endhint %}

## Unsupported Scenarios

The connector does not support lineage extraction for certain Tableau scenarios that require runtime resolution, unsupported source metadata, or transformation details that are not available through the supported lineage extraction process.

### Unsupported Lineage

<table data-search="false"><thead><tr><th width="199">Not Supported</th><th width="348">Description</th><th width="263">Recommendation / Workaround</th></tr></thead><tbody><tr><td>Cross-database Joins and Federated Queries</td><td>Lineage cannot be fully resolved for cross-database joins and federated query scenarios.</td><td>Validate cross-database dependencies manually where required.</td></tr><tr><td>Hierarchies within Dashboards or Workbooks</td><td>Hierarchy-level dependencies are not fully supported for lineage extraction.</td><td>Validate hierarchy relationships separately where required.</td></tr><tr><td>Filter-only Fields Not Visualized</td><td>Fields used only for filtering and not represented in visualized output are not fully captured as lineage relationships.</td><td>Review filter dependencies separately where required.</td></tr><tr><td>Dynamic Parameters and Context Filters</td><td>Dynamic parameter and context-filter dependencies are not resolved as complete lineage relationships.</td><td>Validate parameter and filter dependencies manually.</td></tr><tr><td>Cross-dashboard Dependencies</td><td>Dependencies that span dashboards are not fully supported for lineage extraction.</td><td>Document or validate cross-dashboard dependencies separately where required.</td></tr><tr><td>Custom SQL with Nested or Procedural Logic</td><td>Custom SQL containing nested or procedural logic cannot be fully parsed for lineage extraction.</td><td>Simplify SQL where possible or validate the affected lineage manually.</td></tr><tr><td>Tableau Prep Flow Lineage Beyond Published Datasources</td><td>Lineage for Tableau Prep flows beyond published datasources is not supported.</td><td>Validate Tableau Prep dependencies separately where required.</td></tr><tr><td>Non-SQL Sources</td><td>Sources such as Google Sheets and Web Data Connectors are not supported for complete lineage extraction.</td><td>Use supported source connections or document affected lineage manually.</td></tr><tr><td>Extract Datasources</td><td>Extract Datasources are not supported for complete lineage extraction.</td><td>Validate extract dependencies separately where required.</td></tr><tr><td>Extract Columns</td><td>Columns created or represented within unsupported Extract Datasources are not supported for lineage creation.</td><td>Validate extract column dependencies manually where required.</td></tr></tbody></table>

{% hint style="info" %}
Unsupported scenarios do not generate complete lineage and may result in missing or disconnected lineage relationships within lineage visualization.
{% endhint %}

## Current Functional Status

This section outlines the current lineage capabilities and coverage of the Tableau connector.

<table data-search="false"><thead><tr><th width="178">Status Area</th><th>Details</th></tr></thead><tbody><tr><td>Overall Coverage</td><td>Intermediate coverage across Tableau Workbooks, Dashboards, Worksheets, Datasources, source tables, SQL queries, and supported file datasources.</td></tr><tr><td>Lineage Depth</td><td>Table-level, chart-level, and column-level lineage across supported Tableau components and source connections.</td></tr><tr><td>Supported Inputs</td><td>Workbooks, Dashboards, Worksheets / Views, Datasources, direct table connections, Custom SQL Queries, calculated fields, supported Excel and CSV file datasources, and related Tableau metadata.</td></tr><tr><td>Functional Scope</td><td>End-to-end lineage from supported source systems and queries through Tableau Datasources and Workbooks to Worksheets and Dashboards, including column-level tracing.</td></tr><tr><td>Transformation Support</td><td>Expressions, aggregations, calculated fields, renamed columns, temporary columns from SQL queries, and metadata-mapped semantic columns are supported.</td></tr><tr><td>Limitation Areas</td><td>Complex calculated fields, nested calculations, LOD expressions, dynamic parameters, context filters, blended data sources, complex Custom SQL, Published Datasources, Extract Connections, Hyper Datasources, SQL Proxy Connections, relationships, and hierarchies have partial or unsupported coverage.</td></tr><tr><td>Resulting Output</td><td>Extensive lineage coverage across standard Tableau reporting and datasource scenarios, with column-level tracing and SQL parsing. Advanced scenarios involving complex calculations, dynamic parameters, non-SQL sources, cross-database relationships, and unsupported Extract Datasources may require manual validation.</td></tr></tbody></table>

{% hint style="warning" %}
The Tableau connector provides extensive lineage coverage across Workbooks, Dashboards, Worksheets, Datasources, direct table connections, Custom SQL Queries, supported file datasources, and column-level relationships. The connector supports calculated fields, nested calculations, expressions, aggregations, renamed columns, and metadata-mapped semantic columns. Advanced scenarios involving complex calculations, LOD expressions, dynamic parameters, context filters, blended data sources, cross-database joins, complex Custom SQL, Tableau Prep flows, non-SQL sources, and Extract Datasources have partial or unsupported coverage and may require manual validation.
{% endhint %}

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release8.1/connectors/connector-repositories/reporting-tool/tableau/tableau-lineage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.