Power BI operating model (deprecated)
The Power BI harvester collects Power BI metadata and sends it to the Collibra Data Lineage server. Collibra processes the metadata and creates new Power BI assets and relations in Data Catalog. You can see them on the asset page overview or visualize them in a diagram or in a technical lineage.
- The assets have the same names as their counterparts in Power BI. Full names and Display names cannot be changed in Data Catalog.
- Depending on your Power BI subscription, it could be that not all asset types are created.
- Asset types are only created if you have all specific Power BI and Data Catalog permissions.
- All Power BI asset types are created in the same domain.
-
Relations that were manually created between Power BI assets and other assets in accordance with the relation types in the Power BI operating model, are deleted after a refresh of the Power BI metadata.
Power BI metadata overview
The following image shows the relations between Power BI asset types.
Harvested metadata per asset type
This table shows the harvested Power BI metadata for each Power BI asset type, assuming you have the necessary subscriptions and configurations for a full ingestion. This table also shows the Resource IDs for each asset type and metadata.
|
Asset type |
Synchronized metadata |
Resource ID |
|---|---|---|
|
Power BI Capacity Resource ID: 00000000-0000-0000-0000-100000000002 |
Full name |
|
| Display name | ||
| Server hosts / is hosted in Business Dimension | 00000000-0000-0000-0000-120000000000 | |
| BI Folder assembles / is assembled in BI Folder | 00000000-0000-0000-0000-120000000001 | |
|
Power BI Column Resource ID: 00000000-0000-0000-0000-100000000008 |
Full name |
|
| Display name | ||
| Description | 00000000-0000-0000-0000-000000003114 | |
| Technical Data Type | 00000000-0000-0000-0000-000000000219 | |
| BI Data Model contains / is part of BI Data Attribute | 00000000-0000-0000-0000-000000007196 | |
| Data Element targets / sources Data Element | 00000000-0000-0000-0000-000000007069 | |
| Data Entity contains / is part of Data Attribute | 00000000-0000-0000-0000-000000007047 | |
|
Power BI Dashboard Resource ID: 00000000-0000-0000-0000-100000000004 |
Full name |
|
| Display name | ||
| Business Dimension groups / is grouped into Report | 00000000-0000-0000-0000-120000000002 | |
|
Report uses / used in Report |
00000000-0000-0000-0000-120000000007 | |
| Report related to / impacted by Business Asset | 00000000-0000-0000-0000-120000000006 | |
|
Power BI Data Model Resource ID: 00000000-0000-0000-0000-100000000007 |
Full name |
|
| Display name | ||
|
BI Data Model contains / is part of BI Data Attribute |
00000000-0000-0000-0000-000000007196 | |
|
BI Folder contains / contained in Data Asset |
00000000-0000-0000-0000-120000000014 | |
| Data Asset is source for / source BI report | 00000000-0000-0000-0000-120000000013 | |
| Data Entity is part of / contains Data Model | 00000000-0000-0000-0000-000000007046 | |
|
Power BI Report Resource ID: 00000000-0000-0000-0000-100000000006 |
Full name |
|
| Display name | ||
| Business Dimension groups / is grouped into Report | 00000000-0000-0000-0000-120000000002 | |
| Data Asset is source for / source BI Report | 00000000-0000-0000-0000-120000000013 | |
|
Report related to / impacted by Business Asset |
00000000-0000-0000-0000-120000000006 | |
|
Report uses / used in Report |
00000000-0000-0000-0000-120000000007 | |
|
Power BI Server Resource ID: 00000000-0000-0000-0000-100000000001 |
Full name |
|
| Display name | ||
| Server hosts / is hosted in Business Dimension | 00000000-0000-0000-0000-120000000000 | |
|
Power BI Table Resource ID: 00000000-0000-0000-0000-100000000009 |
Full name |
|
|
Display name |
||
| Description | 00000000-0000-0000-0000-000000003114 | |
| Data Entity contains / is part of Data Attribute | 00000000-0000-0000-0000-000000007047 | |
| Data Entity is part of / contains Data Model | 00000000-0000-0000-0000-000000007046 | |
|
Power BI Tile Resource ID: 00000000-0000-0000-0000-100000000005 |
Full name |
|
|
Display name |
||
| Business Dimension groups / is grouped into Report | 00000000-0000-0000-0000-120000000002 | |
| Data Asset is source for / source BI Report | 00000000-0000-0000-0000-120000000013 | |
| Report related to / impacted by Business Asset | 00000000-0000-0000-0000-120000000006 | |
| Report uses / used in Report | 00000000-0000-0000-0000-120000000007 | |
|
Power BI Workspace Resource ID: 00000000-0000-0000-0000-100000000003 |
Full name |
|
| Display name | ||
| Description | 00000000-0000-0000-0000-000000003114 | |
| BI Folder assembles / is assembled in BI Folder | 00000000-0000-0000-0000-120000000001 | |
| BI Folder contains / contained in Data Asset | 00000000-0000-0000-0000-120000000014 | |
| Business Dimension groups / is grouped into Report | 00000000-0000-0000-0000-120000000002 |
Note The metadata that is shown on the assets' pages depends on the asset type's assignment. As a result, you might not see all harvested metadata on the asset's page by default.
Recommended hierarchy within a domain
You can enable hierarchies for the domain (or domains) in which your Power BI assets were ingested. Doing so makes it easier to understand the relation between your Power BI assets, when viewing the assets on the domain page.
Follow these steps to enable and configure the recommended hierarchy.
Steps
- Open the domain page of the relevant BI Catalog domain.
- On the content toolbar, click
.
The Configure Hierarchy dialog box appears. - Select Enable Hierarchy.
- Select Single path.
- Start typing and select each of the following relation types:
- Server hosts Business Dimension
- BI Folder assembles BI Folder
- Business Dimension groups Report
- BI Report source Data Asset
- Data Model contains Data Entity
- Data Entity contains Data Attribute
- Click Apply.
The following image shows an example of a BI Catalog domain with hierarchies enabled.
Note In an asset view, like the one shown in the previous image, if any asset is deleted, for example via synchronization or manual deletion, the view is recreated and the hierarchy is lost. In this case, you can again enable and configure the recommended hierarchy.