Purview -Power BI - Dataset Schema missing from Purview

Question

Hi Team,

We have migrated the AAS Tabular model to PowerBI - its the dataset named EDW_Relational_ReportModel. We can see the dataset in Purview, but not its schema. We are able to see the schema for all other PowerBI models. Please confirm if it's supported in Purview or not?

Answer 1

@Sharma, Praghya (CONTRACTOR) - Thanks for the question and using MS Q&A platform.

UPDATE: According to the offical documentation - For lineage between Power BI artifacts and external data assets, currently the supported source types are:

• Azure SQL Database
• Azure Blob Storage
• Azure Data Lake Store Gen1
• Azure Data Lake Store Gen2

Purview supports scanning and indexing the schema of Power BI datasets. However, there are some limitations to consider:

• The schema of a Power BI dataset is only visible in Purview if the dataset is connected to a supported data source. If the dataset is connected to an unsupported data source, the schema will not be visible in Purview.
• The schema of a Power BI dataset is only visible in Purview if the dataset is published to a workspace that is registered with Purview. If the workspace is not registered with Purview, the schema will not be visible in Purview.
• The schema of a Power BI dataset is only visible in Purview if the dataset is using the latest version of the Power BI API. If the dataset is using an older version of the API, the schema may not be visible in Purview.

To troubleshoot the issue, you can try the following steps:

• Check if the data source used by the dataset is supported by Purview. You can refer to the Purview documentation for a list of supported data sources.
• Check if the workspace where the dataset is published is registered with Purview. You can check this by navigating to the Purview portal and verifying that the workspace is listed under the "Registered Workspaces" section.
• Check if the dataset is using the latest version of the Power BI API. You can check this by navigating to the dataset settings in Power BI and verifying that the "API Version" is set to the latest version.

If the issue persists, you can try opening a support ticket for further troubleshooting on the issue.

Hope this helps. Do let us know if you any further queries.

---

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.