Migrating your existing Power BI assets to the new integration method

A key feature of the Collibra Data Intelligence Cloud 2022.05 release was the ability to ingest Power BI metadata in Data Catalog via the lineage harvester. However, the new integration method was only available to customers who did not need to migrate existing Power BI assets. The following process now allows you to migrate your existing Power BI assets, making integration via the lineage harvester available to all Power BI customers.

Steps

The table below shows the steps and prerequisites required to integrate Power BI in Data Catalog. These steps are best practices, which means that some of them might be optional, but highly recommended.

Step	What?	Description	Prerequisites
1	Download and install the newest versions of: The Power BI harvester. The lineage harvester.	You need to run both harvesters, to synchronize the Power BI metadata via the original ingestion method, as described in Working with Power BI service. You can download both harvesters from the Collibra Product Resource Downloads page.	See: Install the Power BI harvester. Install the lineage harvester.
2	Prepare both configuration files.	Prepare the Power BI configuration file and the lineage harvester configuration file, for ingestion via the original method, and then run the harvesters. Empty configuration files are included in the respective folders, after installing each harvester.	See: Prepare the Power BI configuration file. Prepare the lineage harvester configuration file.
3	Update permissions.	Ensure that you have completed all of the prerequisite tasks ingesting Power BI metadata via the lineage harvester.
4	Make random call to the Metadata API.	Make a call to the Metadata API, to ensure that you can communicate with the Power BI server. For example: `GET https://api.powerbi.com/v1.0/myorg/admin/workspaces/modified`
5	Manually refresh your Power BI datasets.	Manually refresh your Power BI datasets to ensure that the data in your Power BI datasets is up-to-date. This is necessary because the Power BI APIs use cached results. For complete information, see: The Microsoft documentation. The Microsoft Power BI Blog.	See Power BI prerequisites.
6	Edit the lineage harvester configuration file.	Edit the lineage harvester configuration file so that it includes the required properties for ingesting via the lineage harvester. See Prepare the lineage harvester configuration file for Power BI. Warning The value of the `id` property in your lineage harvester configuration file must be the same as the value of the `sourceId` property in your Power BI configuration file.	See Prepare the lineage harvester configuration file for Power BI.
7	Run the lineage harvester with the `full-sync` command	Start the lineage harvester again in the console and run the following command: for Windows: `.\bin\lineage-harvester.bat full-sync` for other operating systems: `./bin/lineage-harvester full-sync` This triggers the creation of Power BI assets, their relations and a technical lineage in Data Catalog. We highly recommend that you always install and use the newest lineage harvester.	See Prepare the lineage harvester configuration file for Power BI.