Impact Analysis Export (Excel)

A complete guide to the timestamped Excel file generated by the Impact Analysis export — its two sheets, all 16 columns, and how to read dependency paths.

Excel16 columnsDependency pathsTraceability

When you click Export to Excel in the Impact Analysis section, Rapid BI Catalog generates and downloads a timestamped .xlsx file named Impact_Analysis_<date>_<time>.xlsx. The file contains two sheets: Summary and Impacted Objects.

Prerequisite
The Export to Excel button is only available after you have submitted filters and the Impact Analysis section has returned results. The export reflects the exact filters that were submitted — not any unsaved filter changes.
Licence Note
Export to Excel requires the Impact Analysis licence feature. The button will not appear if your licence does not include it.

Sheet 1: Summary

The Summary sheet gives a high-level count of every Tableau object type impacted by your selection.

Excel export — Summary sheet
Summary sheet: a count of every impacted Tableau object type.
ColumnDescription
Object TypeThe category of Tableau object
CountNumber of distinct objects of that type impacted

Row Order

Rows always appear in the following fixed order:

Object Type
Tableau Data Sources
Tableau Data Source Tables
Tableau Data Source Fields
Calculated Fields
Sets
Groups
Bins
Hierarchies
Workbooks
Worksheets
Dashboards
Storyboards
Total
File-Level Licence Note (Starter plan)
On the Starter plan (file-level granularity), only the Workbooks row appears — all other object-type rows are suppressed because sub-file detail requires object-level lineage (the Professional or Enterprise plan).

Sheet 2: Impacted Objects

The Impacted Objects sheet provides the full detail — one row per impacted object per dependency path. A single object (e.g., a Worksheet that uses fields from two different Tableau Data Sources) may appear on multiple rows, with each row representing a distinct path through the dependency graph.

Excel export — Impacted Objects sheet
Impacted Objects sheet: one row per impacted object per dependency path, across all 16 columns.

Columns

#Column NameDescription
1Searched Object NameThe name of the data asset you searched for, at the level you selected in the filters
2Searched Object TypeThe type of the searched asset: Connection, Database, Table, or Field
3Data Connection NameThe source data connection that contains the searched asset
4Database NameThe source database within that connection
5Table NameThe source table within that database
6Field NameThe specific source field (populated only when filters were set to Field level)
7Tableau Server/CloudThe Tableau Server or Tableau Cloud connection the workbook belongs to
8SiteThe Tableau site that contains the workbook
9ProjectThe Tableau project that contains the workbook
10Workbook NameThe Tableau Workbook containing the impacted object
11Tableau Data Source NameThe Tableau Data Source (inside the workbook) through which the dependency flows
12Tableau Data Source Table NameThe table inside the Tableau Data Source
13Impacted Object NameThe name of the specific impacted object
14Impacted Object TypeThe type of the impacted object (see table below)
15Built From Object NameThe immediate upstream object that this impacted object depends on
16Built From Object TypeThe type of that upstream object
Tableau Server/Cloud columns
Columns 7–9 (Tableau Server/Cloud, Site, and Project) record the Tableau Server or Tableau Cloud the workbook came from. If the workbook was not from Tableau Server/Cloud — for example, a local workbook file — these columns are left empty.

Possible Values for "Impacted Object Type"

ValueWhat it represents
FieldA Tableau Data Source field
Calculated FieldA custom calculated field
SetA Tableau Set
GroupA Tableau Group
BinA Tableau Bin
HierarchyA Tableau Hierarchy
WorksheetA worksheet within a workbook
DashboardA dashboard within a workbook
StoryboardA storyboard within a workbook

Note: Workbooks (column #10), Tableau Data Sources (#11), and Tableau Data Source Tables (#12) exist as their own columns, not as Impacted Object Type values.

Header Row Behaviour

  • The header row is frozen — it remains visible as you scroll down through large result sets.
  • Auto-filter dropdowns are enabled on every column, allowing you to filter and sort directly within Excel.

Understanding "Built From" Columns (15–16)

The Built From Object Name and Built From Object Type identify the immediate upstream dependency in Tableau — the object that the impacted object is directly derived from or depends on.

Impacted objectBuilt From example
Calculated FieldThe field it references
SetThe Field that defines set membership
HierarchyOne member field per row (a 3-member hierarchy generates 3 rows)
WorksheetThe upstream field or Calculated Field used in the view
Hierarchies
Each impacted Hierarchy generates one row per member field it contains. A Hierarchy with three member fields will produce three rows — each with the same Hierarchy in "Impacted Object Name" but a different member field in "Built From Object Name".

Row Sorting

Rows in the Impacted Objects sheet are sorted in the following priority order (all alphabetical, case-insensitive):

  1. Searched Object Name
  2. Impacted Object Type
  3. Impacted Object Name
  4. Built From Object Type
  5. Built From Object Name

Starter Plan (File-Level) — Reduced Column Set

On the Starter plan (file-level granularity), the Impacted Objects sheet is simplified — object-level columns require the Professional or Enterprise plan. The following columns are not shown:

  • Tableau Data Source Name
  • Tableau Data Source Table Name
  • Impacted Object Name
  • Impacted Object Type
  • Built From Object Name
  • Built From Object Type

Only the Searched Object columns (1–2), source hierarchy columns (3–6), the Tableau Server/Cloud, Site, and Project columns (7–9), and Workbook Name (10) are shown.

Next Steps