There are a few considerations and limitations that you must take into account when you use the Power BI metadata connector and lineage feature.
Supported subscriptions
Important Your subscription determines which Power BI metadata the Power BI harvester can collect.
You need one of the following subscriptions to ingest Power BI metadata in Data Catalog:
- Power BI Pro. To ensure a full ingestion, you also need a Power BI Embedded Capacity subscription in Microsoft Azure.
- Power BI Premium.
- Power BI Premium Per User.
Note The Power BI Premium Per User license is a new license type that is released for general availability, but is still in its preview period. For more information, see the Microsoft documentation.
Other Power BI subscriptions are currently not supported.
Power BI metadata
The Power BI harvester can only partially access metadata of the following Power BI elements:
- Classic Power BI workspaces, which include My Workspace. Only a full ingestion of new Power BI workspaces is supported.
- Power BI workspaces that are not part of a dedicated capacity.
- Descriptions of most Power BI elements.
- Power BI apps.They can be ingested as Power BI Reports, but there is no easy way to distinguish them from real Power BI reports.
The Power BI harvester cannot access metadata of the following Power BI elements:
- Dataflows.
- Tile subtitles.
- Data from external sources supplying the input for the Power Query expressions in Power BI.
Important The Collibra Data Lineage server can process most, but not all, complex Power BI metadata. This means that the success rate of a Power BI ingestion can be very high, but almost never 100%.
Known issues
The following table presents the known issues of the Power BI integration in Collibra Data Intelligence Cloud.
|
Known issue |
Description |
|---|---|
The Power BI harvester shows an Internal Server Error because of the Power BI workspace filter. |
If you want to ingest a lot of Power BI data and you use the WorkspaceFilter in the Power BI configuration file, the Power BI API can go in timeout and, as a result, you get an If you get this error, we highly advise to not use the workspace filter. Note If the error message indicates that the issue is an internal server error, the problem is caused by the Power BI REST API, not the Power BI harvester itself. |
| The data set Report Usage Metrics Model cannot be ingested. |
The Report Usage Metrics Model is a data set that is automatically created by Power BI. This data set does not contain actual data, which means that they contain nothing to ingest into Data Catalog. However, the Power BI harvester still tries to access the metadata and, since there is nothing to access, shows an error message. All error messages about the Report Usage Metrics can be ignored. |
|
The |
Currently, the
"workspaceFilter": "name eq 'workspace1' or name eq 'workspace2'" However, you cannot ingest Power BI workspaces that have "workspace1" or "workspace2" in their name, because the IN operator is currently not supported: "name in ('workspace1', 'workspace2')"
Tip For more syntax examples that you can use in the |
| Power BI assets that are moved to a different domain are deleted after synchronization. |
When you run the harvesters, Collibra Data Lineage creates all Power BI assets in the same Data Catalog BI domain. We highly recommend that you do not move these assets to another domain. If you move assets to another domain, they will be deleted and recreated in the initial Data Catalog BI domain when you synchronize Power BI. As a consequence, all manually added data of those assets is lost. |
|
You have successfully ingested Power BI metadata, but calculated tables and columns are not shown in the Technical lineage or in the browse tab pane. |
Calculated columns are virtually the same as a non-calculated columns, with one exception: their values are calculated using DAX formulas and values from other columns. Collibra Data Lineage currently does not support internal transformations via DAX language, and any data objects derived via DAX are not shown in the technical lineage or in the browse tab pane. Currently, only M Query/Power Query expressions are supported. |
| You are experiencing Power Query parsing errors when ingesting Power BI metadata. |
The Power Query parser does not currently support parsing for:
|