> 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.2/connectors/connector-repositories/reporting-tool/power-bi/power-bi-cloud/power-bi-cloud-lineage.md).

# Power BI Cloud - Lineage

This article outlines the lineage coverage, configuration requirements, supported components, transformation support, supported scenarios, known limitations, and current functional status for lineage extraction in Power BI Cloud.

The Power BI Cloud connector provides automated, production-ready lineage extraction across Power BI reports, datasets, and dataflows. It delivers end-to-end visibility into data flow by tracing dependencies from source systems through M Query transformations, DAX-based semantic models, and report visualizations across multiple workspaces within the Power BI cloud environment.

### Lineage Configuration Requirements

Successful lineage extraction depends on proper connector configuration, metadata availability, and valid source connections. The following requirements must be satisfied to ensure accurate source-to-target lineage generation.

#### Configuration Requirements Table

<table><thead><tr><th width="210">Configuration</th><th>Required Detail</th></tr></thead><tbody><tr><td>SQL Dialects</td><td>SQL dialects must be defined in CrawlerOption.supportingDialects.</td></tr><tr><td>Connection Priority</td><td>Connection priority for lineage must be configured using CrawlerOption.connectionsPriorityForLineage.</td></tr><tr><td>ElastiCube Connection</td><td>ElastiCube connection details must be available for schema resolution.</td></tr><tr><td>API Access</td><td>API tokens or credentials must provide access to extract metadata for dashboards, reports, datasets, and data models.</td></tr></tbody></table>

{% hint style="warning" %}
Missing metadata, unavailable source connections, insufficient API permissions, or invalid credentials may result in incomplete lineage generation.
{% endhint %}

### Lineage Components

| Component / Feature        | Supported |
| -------------------------- | :-------: |
| Reports                    |     ✅     |
| Dashboards                 |     ⚠️    |
| Datasets (Semantic Models) |     ✅     |
| Dataflows                  |     ✅     |
| Workspaces                 |     ✅     |
| Paginated Reports          |     ✅     |
| Measures (DAX)             |     ✅     |
| Calculated Columns         |     ✅     |
| Calculated Tables          |     ✅     |
| Pages                      |     ✅     |
| Visuals                    |     ✅     |
| Relationships              |     ✅     |
| Parameters                 |     ⚠️    |
| Apps                       |     ⚠️    |
| Filters                    |     ⚠️    |
| Hierarchies                |     ⚠️    |

{% hint style="info" %}
The ⚠️ icon indicates partially supported functionality with limited lineage coverage in applicable scenarios.
{% endhint %}

### Column Creation Support

This section outlines lineage support for column creation and transformation scenarios.

#### Column Creation from Lineage

| Transformation Type   | Supported |
| --------------------- | :-------: |
| Expressions (M Query) |     ⚠️    |
| Aggregations (DAX)    |     ⚠️    |
| Calculated Fields     |     ⚠️    |
| Renamed Columns       |     ✅     |
| Temporary Columns     |     ✅     |
| Semantic Columns      |     ✅     |

{% hint style="info" %}
The ⚠️ icon indicates partially supported functionality where lineage coverage depends on transformation complexity and metadata availability.
{% endhint %}

### Supported Use Cases

The connector supports lineage extraction across standard Power BI Cloud reporting, semantic modeling, and data transformation workloads.

#### Supported Lineage Scenarios

<table><thead><tr><th width="330">Supported Scenario</th><th>Details</th></tr></thead><tbody><tr><td>Report → Dataset Lineage</td><td>Lineage between report visuals and associated datasets</td></tr><tr><td>Dataset → Dataflow → Source Lineage</td><td>End-to-end lineage from datasets through dataflows to source systems</td></tr><tr><td>Cross-workspace Lineage</td><td>Lineage across shared datasets and reports</td></tr><tr><td>Import and DirectQuery Models</td><td>Lineage for Import and DirectQuery semantic models</td></tr><tr><td>M Query (Power Query) Transformations</td><td>Lineage for Power Query transformation logic</td></tr><tr><td>DAX-based Measures and Calculated Columns</td><td>Lineage for DAX measures and calculated columns</td></tr><tr><td>Paginated Report (.rdl) Lineage</td><td>Lineage extraction for paginated reports</td></tr><tr><td>Column-level Lineage</td><td>Lineage across tables and report visuals</td></tr><tr><td>Composite Model Lineage</td><td>Lineage for models combining Import and DirectQuery</td></tr><tr><td>Cross-cloud Source Lineage</td><td>Lineage across Azure SQL, Snowflake, Databricks, BigQuery, and other supported cloud sources</td></tr></tbody></table>

{% hint style="info" %}
Lineage extraction is based on metadata available through Power BI Cloud APIs, M Query definitions, DAX expressions, and configured source connections.
{% endhint %}

## Partial or Limited Coverage

Certain scenarios provide partial lineage coverage due to metadata dependencies, runtime behavior, or expression complexity.&#x20;

### Scenarios

| Scenario                              | Limitation Description                                                        | Recommendation                                                         |
| ------------------------------------- | ----------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| Dynamic or Parameterized M Queries    | Runtime parameters are not fully resolved during lineage extraction.          | Use static M Query definitions where possible.                         |
| Nested or Complex DAX Expressions     | Dependency parsing may be incomplete for complex expressions.                 | Simplify DAX logic or validate lineage manually.                       |
| Row-Level Security (RLS) Filters      | Limited lineage extraction for RLS definitions.                               | Validate security dependencies separately where required.              |
| Dashboard Tiles                       | Visual-to-dataset mapping may be incomplete.                                  | Verify dashboard lineage manually where required.                      |
| Embedded Analytics and Custom Visuals | Metadata capture is limited for embedded content and custom visuals.          | Use standard visuals where possible.                                   |
| Unrefreshed Datasets                  | Schema extraction may be incomplete if datasets are not refreshed.            | Refresh datasets before lineage extraction.                            |
| Cross-workspace Lineage               | Lineage may be incomplete when linked workspaces are inaccessible.            | Ensure access permissions are available for all referenced workspaces. |
| Custom Connectors                     | Limited or no parsing support for metadata exposed through custom connectors. | Use supported connectors or document lineage manually.                 |

{% hint style="warning" %}
Complex DAX expressions, runtime parameters, restricted workspace access, and incomplete metadata may reduce lineage completeness and column-level accuracy.
{% endhint %}

## Unsupported Scenarios

The connector does not support lineage extraction for certain runtime-generated, restricted, or unsupported Power BI Cloud scenarios.

### Unsupported Lineage

| Not Supported                                        | Description                                                                              | Recommendation                                           |
| ---------------------------------------------------- | ---------------------------------------------------------------------------------------- | -------------------------------------------------------- |
| Cross-tenant Datasets and Dataflows                  | Lineage cannot be generated across different Power BI tenants.                           | Document dependencies manually where required.           |
| Dynamic Columns Created by Custom M Functions        | Runtime-generated columns are not resolved during lineage extraction.                    | Use static transformation logic where possible.          |
| Advanced DAX with Circular or Recursive Dependencies | Circular or recursive DAX relationships are not parsed.                                  | Simplify DAX logic where applicable.                     |
| Unsupported Custom Connectors                        | Metadata cannot be extracted from unsupported connectors.                                | Use supported connectors or document lineage manually.   |
| Unpublished or Embedded (Non-API) Reports            | Reports that are unavailable through supported APIs are not analyzed.                    | Publish reports before lineage extraction.               |
| RLS Evaluation in DirectQuery Mode                   | Runtime Row-Level Security evaluation is not supported.                                  | Validate security behavior separately where required.    |
| Linked Semantic Models Without Access Permissions    | Restricted semantic models cannot be analyzed.                                           | Ensure appropriate access permissions are available.     |
| Data Sources Outside Power BI Cloud                  | Sources that are not accessible through Power BI Cloud APIs are not included in lineage. | Configure supported source connections where applicable. |

{% hint style="info" %}
Unsupported scenarios do not generate lineage and may appear as disconnected nodes within lineage visualization.
{% endhint %}

## Current Functional Status

This section outlines the current lineage capabilities supported by the Power BI Cloud connector.

<table><thead><tr><th width="218">Status Area</th><th>Details</th></tr></thead><tbody><tr><td>Overall Coverage</td><td>Strong coverage across datasets, dataflows, reports, and semantic models</td></tr><tr><td>Lineage Depth</td><td>Table-level and column-level lineage through M Query and DAX parsing</td></tr><tr><td>Supported Inputs</td><td>Reports, dashboards, datasets, dataflows, paginated reports, semantic models, visuals, and relationships</td></tr><tr><td>Functional Scope</td><td>Lineage extraction across reporting, semantic modeling, and data transformation workflows</td></tr><tr><td>Limitation Areas</td><td>Complex DAX expressions, runtime parameters, custom connectors, Row-Level Security (RLS), dashboard tiles, and restricted workspace access</td></tr><tr><td>Resulting Output</td><td>Reliable lineage for standard Power BI Cloud workloads with partial coverage for advanced modeling and transformation scenarios</td></tr></tbody></table>

{% hint style="warning" %}
The Power BI Cloud connector provides strong lineage coverage across reports, datasets, dataflows, semantic models, and visualizations, including column-level lineage through M Query and DAX parsing. Advanced scenarios involving complex DAX expressions, runtime parameters, custom connectors, Row-Level Security (RLS), dashboard tiles, and restricted workspace access 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.2/connectors/connector-repositories/reporting-tool/power-bi/power-bi-cloud/power-bi-cloud-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.