# Report lineage The report lineage feature in Data Catalog provides a graphical view of how a report is constructed by visualizing its relationship to underlying data sources, datasets, and intermediate data entities. It helps users understand the complete data flow used to build a report, from raw tables and files, through transformations, to the final report and its visualizations. **Note:** The report lineage is available only for Report and Report Page components of connected Business Intelligence (BI) servers, such as Tableau, and it can be accessed in the **Business Intelligence** section of Data Catalog. To learn more about Business Intelligence and its components, see [Business Intelligence](/pdc-use/pdc-business-intelligence.md). ![](/files/uAjf2viIoUzXs7H0Xr1D) By showing upstream and downstream connections of a report component, the lineage graph enhances data transparency, trust, and auditability. With this, you can trace the origin of data displayed in a report and assess the impact of changes to source data. In addition to automatically generated lineage, you can also manually add lineage. This is useful when: * Metadata ingestion is incomplete or unsupported * Data transformations occur outside of connected systems (such as in custom scripts or spreadsheets) * You want to simulate lineage during development or validation Manually adding lineage helps complete the data flow picture, improves traceability, and supports compliance and impact analysis even for disconnected or external processes. ## Key benefits of report lineage The following are the key benefits of the report lineage. It: * Provides a clear and visual representation of the report structure and its data lineage. * Helps verify data accuracy and report reliability by tracing the source of the data. * Supports compliance and governance initiatives (for example, GDPR, IFRS, CCPA) by showing how Personally Identifiable Information (PII) flows through reports. * Enables impact analysis by identifying downstream components affected by dataset or schema changes. The Report Lineage graph includes relationships between various components, such as: * **Table/File** (source systems or file-based inputs) * **Data Entity** (logical data layer within Data Catalog) * **Dataset** (aggregated or transformed data) * **Report** (such as Tableau Workbook) * **Chart** (individual visual components of a report) By understanding how these components are interconnected, you can make more informed decisions, ensure governance compliance, and resolve issues more efficiently. ## Prerequisites for report lineage To view and explore report lineage in Data Catalog, make sure the following conditions are met: * You must have the necessary access permissions in Data Catalog to configure, import, and view report components. For more information, see [User roles and permissions in Data Catalog](/pdc-use/pdc-user-roles-and-permissions.md). * You must configure and connect to a supported Business Intelligence (BI) server, such as Tableau server, in Data Catalog. For detailed steps, see the **Configure a Tableau server connection in Data Catalog** topic under the **Advanced Configurations** section in the **Administer Pentaho Data Catalog** document. * After you configure the BI server connection, import metadata to enable report lineage. For detailed steps, see the **Import and sync Tableau server components into Data Catalog** topic under the **Manage Business Intelligence components** section in the **Administer Pentaho Data Catalog** document. ## How the report lineage works Report lineage in Data Catalog visually maps the relationship between a report and the data used to generate it. The report lineage graph illustrates how data flows from source systems through various stages, including datasets and transformations, before being presented in a report or chart. The report lineage graph uses a node-based layout, where each node represents a component involved in report generation. Arrows between nodes represent data flow, helping users trace the origin and usage of data across the reporting pipeline. ![PDC workflow of report lineage](/files/mcDfBccCPJSQlz0mAuLr) ## Components in the report lineage graph The following table shows the components of the report lineage graph:
ComponentDescription
Table/FileRepresents raw data sources, such as tables in databases or files in a file system.
Data EntityRepresents structured logical groupings of data imported into Data Catalog.
DatasetRepresents curated or transformed data prepared for reporting or analysis.
ReportRepresents the main reporting object, such as a Tableau Workbook or Power BI Report.
ChartRepresents a visual element, such as a graph or table, within a report.
Each component appears with an icon that reflects its type, and the graph supports allowed predecessor relationships between components. * **Example flow** A typical lineage path might look like this: ![PDC Lineage path](/files/V9TkjeN6Y0yyojB3xlxD) For example: * A file named Customer.csv and a PostgreSQL table named Sales\_Orders are both imported. * These are grouped into a data entity called Orders and Returns. * The data entity feeds into a dataset named QuarterlySales. * The dataset is used to build a report named Q1\_Sales\_Report. * The report contains a chart named Top 10 Products\ This graph helps users understand: * Which data sources feed into a report * What transformations or intermediate steps are involved * Where the report data is ultimately displayed The graph supports both upstream (data origin) and downstream (data usage) navigation. You can expand or collapse nodes to explore specific parts of the lineage. ## View report lineage You can view the report lineage for any report component that has been imported from a supported Business Intelligence (BI) server, such as Tableau. The lineage view is available only for report and report page components in the Business Intelligence section of Data Catalog. Perform the following steps to view the report lineage 1. In the left navigation menu, select **Business Intelligence**. The Business Intelligence page appears. 2. Select the BI server (for example, Tableau server) where your reports are hosted. 3. Go to a report component within the hierarchy and select the report you want to explore. The Summary page appears. 4. On the Lineage pane, click **View Lineage**. ![PDC View Linage in Linage pane](/files/BhoOUKlmaONwgjgAZ40s) The lineage graph appears, showing upstream and downstream relationships between the report and other components, such as datasets, data entities, tables, and charts. ![PDC Lineage](/files/y6sh7tYnlkffGZAotSVF) 5. Click the smaller rectangle for the resource. A side panel opens, providing more details about the resource, including job, actions, and transformations. ![PDC details of a particular lineage](/files/xhjsSwORBvqdkfQQkBl0) On the Lineage page, you can also use the following actions to explore the lineage:
Field or IconAction
Find in graphSearch the lineage graph
UpstreamSelect a number corresponding to the number of hops upstream from the resource that you want to view
DownstreamSelect a number corresponding to the number of hops downstream from the resource that you want to view

A minus symbol

Zoom out

A square with only the corners shown

Reset the lineage graph size

A plus symbol

Zoom in

PDC Node icon

Display the action that was performed on the data
Add LineageManually add a resource to the lineage graph. See Add manual lineage.
## Add manual lineage to BI report components In the Data Catalog, you can add manual lineage to BI reports in the Business Intelligence section, building a complete view of the data flow, even when the source or intermediate metadata is missing or unsupported. For example, if a report is created from an offline Excel file or a custom data transformation, you can manually link that file or dataset to the report in Data Catalog, so the lineage view reflects the actual data path. Manual lineage enhances trust, improves impact analysis, and supports governance by connecting disconnected components in your reporting pipeline. **Note:** Adding manual lineage creates a visual and logical link in Data Catalog but does not affect the report content in the BI tool. Perform the following steps to add manual lineage for BI reports in Data Catalog: 1. In the left navigation menu, select **Business Intelligence**. The Business Intelligence page appears with the list of existing BI servers and their hierarchy. 2. Go to a report or report page component for which you want to add a manual lineage. 3. On the component’s **Summary** tab, in the Lineage pane, click **View Lineage**. The Lineage page opens. 4. In the lineage graph, click the resource you want to add lineage to. The Details panel appears on the right side. ![PDC Manual Lineage Details panel](/files/8xirNk8QvUMkkoRP1iu6) 5. In the Details panel, click **Add Lineage**. The Add Lineage dialog box appears. PDC Add Lineage 6. In the Add Lineage dialog box, do one of the following: * To link a data asset from the **Data Canvas**, select the **Data Canvas** tab and choose the source item. * To link to another BI component, select the BI Reports tab and browse the BI server folders. 7. Click **Add**. You have successfully added a manual lineage to the resource, and the new lineage connection is now visible in the graph. You can repeat these steps to add multiple manual connections to represent complex data flows. ## Remove manual lineage from BI report components If a manually added lineage connection is no longer valid or was created by mistake, you can remove it from the Lineage view. This ensures that the lineage graph remains accurate and reflects the actual data flow used to build a report. **Note:** * You can only remove lineage connections that were manually added. Lineage generated automatically by metadata import cannot be removed. * Removing a manual lineage link only removes the visual relationship from Data Catalog. It does not delete the source or target data assets. Perform the following steps to remove manual lineage for BI reports in Data Catalog: 1. In the left navigation menu, select **Business Intelligence**. The Business Intelligence page appears with the list of existing BI servers and their hierarchy. 2. Navigate to a report or report page component for which you want to remove the lineage. 3. On the component’s **Summary** tab, in the Lineage pane, click **View Lineage**. The Lineage page opens. 4. In the lineage graph, click the **Node** (data asset or report) that is part of the manually added lineage you want to remove. The Details panel appears. 5. In the Details panel, under **Actions**, click **Remove**. 6. In the confirmation dialog box, click **Remove** again to delete the manual lineage connection. You have successfully removed the manual lineage from the selected resource. The removed connection no longer appears in the lineage graph. You can repeat these steps to clean up or revise additional manual lineage relationships as needed. --- # Agent Instructions: 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: ``` GET https://docs.pentaho.com/pdc-use/pdc-lineage/pdc-report-lineage.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.