Power BI troubleshooting (deprecated)

Make sure to check all properties and values before you run the Power BI harvester.

If any of the values of the required configuration properties are missing, invalid or incorrect, the Power BI harvester or lineage harvester fails with an error or the Power BI ingestion will be incorrect.

The Power BI harvester and lineage harvester should have the same value in the url and (source)Id property.

This is a common mistake when you use the service principal authentication method. To solve this issue, make sure that you have enabled the Allow service principals to use read-only Power BI admin APIs (preview) option in the Power BI Admin portal,.

Web services providing the API interfaces that the Power BI harvester uses may sometimes experience problems, or there may be problems with network access to these resources. If the Power BI harvester fails unexpectedly, check the following network resources and make sure they work properly:

• Power BI REST API endpoints
• XMLA endpoints
• Technical lineage API

Considering the nature of these remote resources, the cause of the problem can often be out of your control. Please wait until the issue is resolved or escalate the issue with the respective authority.

To retrieve metadata of individual Power BI dashboards or data sets, you require permissions to access them. However, sometimes the Power BI dashboards and data sets are in a problematic state or you cannot reach them due to Power BI-related issues.

When you execute the Power BI harvester, a summary of all encountered problems is printed. To reduce the number of problems, you can use the group filters in the Power BI configuration file to restrict the set of harvested Power BI workspaces.

Depending on the type of issue, you may need to solve them one by one.

Make sure the syntax in the workspaceFilter property in the configuration file is correct and you don't use the "IN" operator.

Note Currently, the "IN" operator is not supported. As a result, you cannot use "IN" to filter on specific Power BI workspaces in the workspaceFilter property in the Power BI configuration file. For more information, see the Power BI limitations.

Usually, this is a timeout issue. We highly recommend that you increase the timeout duration. Use the following command line option to set the timeout duration: --timeout <seconds>. For example, if you want the Power BI harvester to wait 15 minutes for the connection, you can use --timeout 900.

If you see errors related to Usage Metrics, you can ignore them, because they do not cause Power BI ingestion to fail.

Usage Metrics are reports that are automatically created in Power BI, but they do not represent any Power BI assets or technical lineage information.

If the technical lineage is missing, you must add your Power BI workspaces to a dedicated capacity to allow the Power BI harvester to extract data from XMLA endpoints.

Harvesting metadata via Power BI REST API does not require the dedicated capacity. As a result, the Power BI harvester can only reach limited Power BI metadata and won't create a technical lineage.

If the technical lineage is incomplete, certain aspects of the Power BI ingestion job may not be supported.

Note You can only ingest new Power BI workspaces. This means that classic workspaces and My Workspace in Power BI is not supported. Also read the other limitations of the Power BI ingestion process to understand why technical lineage is missing or incomplete.

Do the following:

• Use new Power BI workspaces if you want a full ingestion.
• Add your Power BI workspaces to a dedicated capacity to allow the Power BI harvester to extract data from XMLA endpoints.
• Grant the Power BI workspaces the Contributor role in the Power BI security group.