Release Notes

Back Next

Microsoft Power BI Connector

The tables in this section describe recent fixed issues for Microsoft Power BI connector in

Metadata Command Center

. Not all monthly releases include fixed issues.

July 2025 fixed issues: Issue
Description

SCAN-20160
When you extract metadata from PowerQuery expressions, the job fails if an anonymous Power Query function includes an optional argument.

SCAN-20360
When you extract metadata from a Power BI report and the Data Analysis Expressions (DAX) that you use reference upstream table measures, the job fails with the following error:
Cannot resolve the following DAX expression: <...> Reason: Cannot resolve the DAX identifier: <...>

Issue	Description
SCAN-20160	When you extract metadata from PowerQuery expressions, the job fails if an anonymous Power Query function includes an optional argument.
SCAN-20360	When you extract metadata from a Power BI report and the Data Analysis Expressions (DAX) that you use reference upstream table measures, the job fails with the following error: Cannot resolve the following DAX expression: <...> Reason: Cannot resolve the DAX identifier: <...>

April 2025 fixed issues: Issue
Description

SCAN-17264
If a paginated report contains IIF statements, metadata extraction jobs fail with the following error:
WARN (ReportFieldAdderWithParserImpl:85) {/PowerBi_BIEVO/BI EVO - PCS/Paginated_Report_Dataset_Self_BI_Giornaliero_V39_Anagrafica_Rapporti (Report)/Paginated_Report_Dataset_Self_BI_Giornaliero_V39_Anagrafica_Rapporti#2 (Report)} - Could not parse expression:IIF

SCAN-17214
Metadata extraction jobs that include the
Table.ToColumns
,
Table.ToRecords
,
Comparer.OrdinalIgnoreCase
,
List.Accumulate
, or
List.Buffer
query functions fail with the following error:
PowerQueryFailedProcessingHandler

SCAN-17158
When you edit metadata extraction filters of an existing catalog source with object references across multiple source systems, you can't save the changes and the process times out.

SCAN-15585
When you run metadata extraction jobs that include PowerQuery expressions, the jobs succeed with warnings.

SCAN-12828
When you perform connection assignment between Microsoft Power BI and SAP HANA Database catalog sources, the job succeeds, but the lineage shows calculation views as reference objects.

Issue	Description
SCAN-17264	If a paginated report contains IIF statements, metadata extraction jobs fail with the following error: WARN (ReportFieldAdderWithParserImpl:85) {/PowerBi_BIEVO/BI EVO - PCS/Paginated_Report_Dataset_Self_BI_Giornaliero_V39_Anagrafica_Rapporti (Report)/Paginated_Report_Dataset_Self_BI_Giornaliero_V39_Anagrafica_Rapporti#2 (Report)} - Could not parse expression:IIF
SCAN-17214	Metadata extraction jobs that include the Table.ToColumns , Table.ToRecords , Comparer.OrdinalIgnoreCase , List.Accumulate , or List.Buffer query functions fail with the following error: PowerQueryFailedProcessingHandler
SCAN-17158	When you edit metadata extraction filters of an existing catalog source with object references across multiple source systems, you can't save the changes and the process times out.
SCAN-15585	When you run metadata extraction jobs that include PowerQuery expressions, the jobs succeed with warnings.
SCAN-12828	When you perform connection assignment between Microsoft Power BI and SAP HANA Database catalog sources, the job succeeds, but the lineage shows calculation views as reference objects.

February 2025 fixed issues: Issue
Description

SCAN-15626
If you use the
Date.ToText
function in a query, metadata extraction jobs fail to parse the PowerQuery expression. This impacts the lineage information.

SCAN-15622
Metadata extraction jobs that include the
MetricsDataConnector.GetMetricsDatapower
query function fail with the following error:
Could not resolve expression due to following exception. Will create emergency lineage using expected columns. Could not resolve external object with name: MetricsDataConnector.GetMetricsData .

SCAN-15614
Metadata extraction jobs don't complete if the source system contains tables with the same name in datasets that reference each other.

Issue	Description
SCAN-15626	If you use the Date.ToText function in a query, metadata extraction jobs fail to parse the PowerQuery expression. This impacts the lineage information.
SCAN-15622	Metadata extraction jobs that include the MetricsDataConnector.GetMetricsDatapower query function fail with the following error: Could not resolve expression due to following exception. Will create emergency lineage using expected columns. Could not resolve external object with name: MetricsDataConnector.GetMetricsData .
SCAN-15614	Metadata extraction jobs don't complete if the source system contains tables with the same name in datasets that reference each other.

October 2024 fixed issues: Issue
Description

SCAN-6611
Metadata extraction jobs that include reports with custom hierarchies fail with the following error:
Unexpected error during extraction layout from file

SCAN-7646

Metadata extraction jobs fail if they include reports with arithmetic expressions.

SCAN-11720
When you extract metadata from a report, all fields in the data set used to create the report get extracted instead of only the fields used in the report.
May 2024 fixed issues: Issue
Description

MDX-41061
In a Microsoft Power BI catalog source, if you specify an
Exclude Metadata
filter with a single value first and then specify additional filters, the additional filters do not get applied.

MDX-41407
When you use a Microsoft Power BI catalog source to extract metadata from workspaces, the job skips workspaces with names that contain trailing spaces.
April 2024 fixed issues: Issue
Description

MDX-40350
When you extract metadata from a Power BI report that includes Power Query expressions, the Data Analysis Expression (DAX) conditions show GENERIC instead of showing the actual column names in the
Overview
tab of the asset in
Data Governance and Catalog
. This issue occurs when Power Query has upstream data set table references with parameters.

MDX-41298
When you run a Microsoft Power BI catalog source job where the Microsoft Power BI catalog source references a SAP HANA Database source system, the connection name is incorrectly extracted.

Issue	Description
SCAN-6611	Metadata extraction jobs that include reports with custom hierarchies fail with the following error: Unexpected error during extraction layout from file
SCAN-7646	Metadata extraction jobs fail if they include reports with arithmetic expressions.
SCAN-11720	When you extract metadata from a report, all fields in the data set used to create the report get extracted instead of only the fields used in the report.

Issue	Description
MDX-41061	In a Microsoft Power BI catalog source, if you specify an Exclude Metadata filter with a single value first and then specify additional filters, the additional filters do not get applied.
MDX-41407	When you use a Microsoft Power BI catalog source to extract metadata from workspaces, the job skips workspaces with names that contain trailing spaces.

Issue	Description
MDX-40350	When you extract metadata from a Power BI report that includes Power Query expressions, the Data Analysis Expression (DAX) conditions show GENERIC instead of showing the actual column names in the Overview tab of the asset in Data Governance and Catalog . This issue occurs when Power Query has upstream data set table references with parameters.
MDX-41298	When you run a Microsoft Power BI catalog source job where the Microsoft Power BI catalog source references a SAP HANA Database source system, the connection name is incorrectly extracted.