Issue | Description |
|---|---|
SCAN-25720 | When you extract metadata from a report and the dataset references a data lakehouse from another workspace, the job fails with the following error: Unknown macro: {Could not create graph for dataset DataMart_SemanticModel due to LakeId not found in SqlAnalyticsEndpoint} |
SCAN-33224 | When you run a metadata extraction job, the job fails with a stack overflow error even after increasing the maximum Java stack size parameter (-Xss). This issue occurs due to cyclic processing when DAX tables or calculated columns reference each other. |
SCAN-29997 | When you run a metadata extraction job, the job doesn't extract all workspace objects specified in the metadata extraction include filters. This issue occurs because source expressions of type AzureStorage.DataLake() are processed incorrectly, leading to an Unable to resolve database object from power query error. |
Issue | Description |
|---|---|
SCAN-21204 | When you run a metadata extraction job, the job completes with the following warning: Cannot resolve the DAX identifier due to unavailable reference This issue occurs if the job includes reports that access data set measures without a table qualification. |
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-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-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. |