Lineage & Impact Analysis

Visualize data flow, determine what breaks before changes reach production, and trace dependencies from data connections to Tableau and Power BI content.

Impact analysisLineage diagramData ConnectionTableauPower BIGovernance

The Lineage & Impact Analysis page creates interactive diagrams that visualize the journey of your data — tracing the flow from data connections and databases through tables and fields, all the way to the Tableau workbooks and the Power BI reports that depend on them. It answers two key questions: where does this data come from? and what will break if it changes?

New to these concepts? See our guides on Tableau impact analysis and metadata management for BI teams.

Use Cases

  • Impact Analysis: Determine exactly which dashboards, worksheets, reports and visuals will break if a database team modifies a table or removes a column.
  • Dependency Tracing: Starting from a Tableau workbook or a Power BI report, trace back to the exact database tables and fields it depends on.
  • Governance: Identify which content is using a specific data connection to support access control reviews or decommissioning decisions.
  • Cross-tool analysis: See in one search everything a warehouse table feeds, whether it is consumed by Tableau, by Power BI, or by both.

Prerequisites

To use this page, metadata must first be exported to a configured database by processing workbooks with the Database output type.

No Metadata Yet?
Admins / Power Users — Go to Processing & Scheduling to process files and export metadata to a database.
Read-Only Users — Ask an Admin or Power User to configure a metadata source and run an export.

Page Layout

The page is divided into three independently collapsible sections. Click the header of any section to expand or collapse it.

SectionDescription
FiltersSelect your source type and apply cascading filters
Impact Analysis(Source Data Connection mode only) A summary of every object impacted by your selection, in both estates
Lineage DiagramThe visual representation of data flow

Section 1: Filters

Step 1 — Select a Source Type

Source TypeWhat it does
Source Data ConnectionStart from a data connection and trace downstream to everything that depends on it, in both Tableau and Power BI. Also triggers the Impact Analysis section.
TableauStart from a Tableau connection, site, project, or workbook and visualize the full data lineage, including the upstream data sources, tables, and connections that feed your Tableau content.
Power BIStart from a Power BI report and visualize its lineage, including the semantic model, model tables and warehouse sources behind it.
Source types follow your licence
A source type your licence does not cover is shown disabled. Power BI requires the Power BI licence — see Power BI Service.

Step 2 — Apply Cascading Filters

Once a source type is selected, a row of cascading filter dropdowns appears. Each level only becomes active after the one above it is selected.

Source Data Connection Mode

FilterRequiredNotes
Data Connection✅ YesSelect one or more connections. Submit is disabled until at least one is chosen.
Database NameOptionalActivates after a connection is selected
Table NameOptionalActivates after a database is selected
Field NameOptionalActivates after a table is selected

Tableau Mode

FilterRequiredNotes
Tableau Server/Cloud✅ YesSelect one or more connections. Submit is enabled once a connection or a site is chosen.
Site NameOptionalActivates after a connection is selected
Project NameOptionalActivates after a site is selected
Workbook NameOptionalActivates after a project is selected

Power BI Mode

Lineage filter with Power BI selected
The three source types, with Power BI selected and its tenant, workspace and report dropdowns shown.
FilterRequiredNotes
Power BI TenantYes, to proceedSelect one or more configured Power BI environments
WorkspaceYes, to proceedActivates after a tenant is selected
Power BI Report✅ YesActivates after a workspace is selected. Submit stays disabled until at least one report is chosen; Select all takes every report under the workspaces you chose.
Cascading Behaviour
If a lower level is left empty, Rapid BI Catalog automatically includes all children below the deepest selection. For example, selecting a Database but leaving Tables empty will include all tables in that database.

Step 3 — Submit or Reset

  • Submit — Generates the Lineage Diagram and (in Data Connection mode) the Impact Analysis. Disabled until the minimum required filter is selected.
  • Reset Filters — Clears all filter selections and resets the diagram and impact analysis. Disabled when no filters are applied.

Section 2: Impact Analysis (Source Data Connection Mode Only)

Impact analysis KPI panels
Impact Analysis: Grouped KPI panels showing counts of impacted objects.

This section appears automatically when the Source Data Connection source type is selected. It provides a structured count of every object impacted by your selection, grouped into six categories — three for Tableau, three for Power BI.

CategoryWhat it counts
Tableau Data SourcesTableau data sources and their tables
Fields & Derived ObjectsTableau fields, calculated fields, sets, groups, bins and hierarchies
Workbooks & VisualsTableau workbooks, worksheets, dashboards and storyboards
Semantic ModelsThe Power BI datasets that hold the model a report reads from
Model Fields & Derived ObjectsColumns, measures and other model elements defining business logic
Reports & VisualsDownstream presentation assets including Reports, Pages and Visuals
Licence — Lineage Granularity
Object-level lineage — down to the individual objects inside a file — requires the Professional or Enterprise plan. On the Starter plan, lineage is file-level: the panels that count objects inside a file are unavailable, and only the file-level counts are shown. See License Management.

Exporting Impact Analysis

An Export to Excel button is available at the bottom of this section. It downloads a timestamped .xlsx file with detailed impact analysis for offline review. The export button is disabled if no results are present.

Understanding the Export File
For a detailed guide to the Excel export format, see Impact Analysis Export (Excel).

Section 3: Lineage Diagram

Interactive lineage diagram
Lineage Diagram: Data connection → databases/tables/fields → Tableau data sources → worksheets/dashboards/storyboards.

The Lineage Diagram is an interactive, node-based visualization of the data flow generated by your submitted filters.

The shared physical layer

Four node types are emitted by both tools and are the common ground between them: Connection, Database, Table and Physical Field. A warehouse table referenced by a Tableau workbook and by a Power BI report is one node, not two — which is why a single impact search spans both tools, and why the Impact Analysis section can count Tableau and Power BI objects against the same selection.

Node Types

Above the physical layer, each tool contributes its own node types.

LevelTableau node types
Data LevelConnection, Database, Table, Physical Field
Tableau LevelData Source, Table, Field, Calculated Field, Set, Group, Bin, Hierarchy, Parameter
Visual LevelWorkbook, Worksheet, Dashboard, Storyboard
LevelPower BI node types
Data LevelConnection, Database, Table, Physical Field
Model LevelSemantic Model, Model Table, Column, Calculated Column, Measure, Calculation Item, Hierarchy, M Parameter, Row-Level Role
Report LevelReport, Page, Visual, Bookmark
Some nodes name their subtype
A Visual node shows the visual's own type, so a matrix reads Visual - Matrix. A Model Table shows a qualifier when it is not a regular table — for example Model Table - Calculated, Model Table - Field Parameter or Model Table - Calculation Group. A Semantic Model shows whether it is embedded or shared.
Workbook and report visibility
The workbook or report portion of the diagram is always shown in full to preserve context. Even if only a small part of it uses the specific upstream table you filtered for, the entire structure will be displayed.
Tableau Published Data Sources resolve their upstream metadata
A workbook that uses a Published Data Source does not contain its upstream metadata, which resides on Tableau Server/Cloud. Rapid BI Catalog fetches it through the Tableau Metadata API, and the PDS appears as a single shared object. This needs an authenticated Tableau connection with the Metadata API enabled; without it the PDS still appears with its consuming workbooks, only without its upstream metadata. Files processed locally never carry it, because it is not in the file.

Highlighting and Tracing

ActionResult
Hover over a nodeHighlights the node and all its directly connected nodes and edges. Non-connected nodes and edges become dimmed.
Click a nodeLocks the highlight in place so it remains active when you move your mouse. Click the same node again to unlock it. Multiple nodes can be locked simultaneously.
Clear HighlightsA button below the diagram clears all active hover and locked highlights at once.
ControlLocationFunction
Zoom In / Out / FitBottom-left of the diagramStandard zoom controls and reset-to-fit-view
Mini-MapBottom-right of the diagramA thumbnail overview of the full diagram showing your current viewport. The mini-map itself is zoomable and pannable.
Mini-Map ToggleSmall button embedded in the diagram cornerClick to show or hide the mini-map

Next Steps