Azure Power BI Scanner OCF Connector Release Notes¶
Alation Cloud Service Applies to Alation Cloud Service instances of Alation
Customer Managed Applies to customer-managed instances of Alation
July 03, 2024¶
Azure Power BI Scanner OCF Connector: Version 2.3.0¶
Enhancements¶
With Alation version 2024.1.4 and Azure Power BI Scanner OCF connector version 2.3.0. Alation has introduced an enhanced user interface for configuring the Azure Power BI Scanner OCF data source settings.
Note
The connector version is compatible with Alation versions 2023.3.2 or higher. However, you will view the old user interface with Alation versions prior to 2024.1.4
The documentation for the new Azure Power BI Scanner OCF experience is available at : Azure Power BI Scanner OCF Connector.
The enhanced user interface provides the following features:
Better User Experience¶
The enhanced Power BI Scanner OCF user interface provides better navigation and multiple visual cues, making it easy to configure and manage Power BI Scanner OCF data source.
There is an exclusive tab to configure Metadata Extraction.
Easy to Connect¶
The Power BI ScannerOCF user interface now provides a step-by-step process to connect to your Power BI Scanner OCF data source easily and quickly.
Additional Error-Prevention Checks¶
The Power BI Scanner OCF user interface now includes added checks to avoid obvious configuration mistakes. The user interface also includes text to assist and provide cues while configuring.
Detailed Error Reports and Troubleshooting Support¶
The improved Power BI Scanner OCF user interface makes troubleshooting easier for metadata extraction, as you can now have a detailed error report. The report contains a detailed error description and steps to resolve the issue. (AL-136714)
June 19, 2024¶
Azure Power BI Scanner OCF Connector: Version 2.2.4¶
Enhancements¶
Support for Extraction By Service Principal¶
The connector will now extract the metadata only from the workspaces to which the Azure Service Principal configured in the Connector Settings tab has access. Refer to the community post to learn how this change could potentially impact your cataloged objects and what actions you could take to keep them cataloged in Alation.
The Enable Extraction For Service Principal option is no longer available in the Connector Settings section of General Settings tab as Metadata Extraction, by default, is supported only for Service Principal. (AL-154041)
Fixed Issues¶
Connector Fails to Populate the Cross-System Lineage When Using Parameter and Query-Based PowerBI Datasets¶
The connector fails to display the cross-system lineage due to the following issues:
Improper parsing of double quotes in queries: The connector fails to extract connection information from dataset expressions that contain double quotes in the table, schema, or database name.(AL-157978)
Unable to display the database name in the Connections tab of the PowerBI dataset: The connector fails to extract connection information when using M Query expressions in datasets and dataflows with blank spaces before the parameters.
For example:
let Source = Sql.Database(SourceServerName, SourceDBName)(AL-160724)
June 05, 2024¶
Azure Power BI Scanner OCF Connector: Version 2.2.3¶
Enhancements¶
Support for Enabling and Disabling Report Field Extraction¶
The Azure PowerBI Scanner OCF connector now includes the Enable Report Fields Extraction option under the General Settings tab. This configuration allows data source admins to enable or disable the report field extraction. (AL-159408)
Note
The report field extraction could increase the overall MDE time depending on Azure Power BI API performance.
Fixed Issues¶
Metadata Extraction Fails Even for A Valid Token¶
MDE fails when the Power BI API incorrectly returns a 403 HTTP status code in the error response, even if the token has not expired.
Now, the MDE proceeds for a valid token. The connector will now rely upon the error code in the response body along with the HTTP status code in the Power BI API response. (AL-156098).
May 08, 2024¶
Azure Power BI Scanner OCF Connector: Version 2.2.1¶
Fixed Issues¶
Lineage Gaps Between Power BI and Snowflake¶
Lineage gaps between Power BI and Snowflake due the following issues has now been fixed (AL-148070, AL-147313):
Table names containing a period (“.”).
Reserved keywords used as parameters. For example,
ServerandDatabase.
Lineage Gaps Between Power BI and SQL Server¶
There are lineage gaps in Power BI connector and SQL Server due to issues related to reserved keywords used as parameters, for example, Database.
The issue is fixed now. (AL-124119)
Out of Memory Errors Due to Incorrect Parsing of Dataset Parameter Expressions¶
Metadata Extraction resulted in out-of-memory errors due to incorrect replacement of integers in dataset expressions when integers are used as parameters.
This issue is now fixed. (AL-143205)
April 17, 2024¶
Azure Power BI Scanner OCF Connector: Version 2.2.0¶
Enhancements¶
Support for Power BI Column-Level Lineage¶
Column-level lineage is available for reports created from table-based datasets and dataflows starting in Alation version 2024.1.2.
Fixed Issues¶
Lineage Not Visible for Datasets Created from Dataflows in Different Workspace¶
Lineage fails for datasets created from a dataflow present in a different workspace. (AL-149160, AL-141424)
December 06, 2023¶
Azure Power BI Scanner OCF Connector: Version 2.1.3¶
Compatible Alation Version - 2023.3.2 or higher
Enhancements¶
Support for Plus Character (+) in Ingested SQL Queries¶
Azure Power BI Scanner OCF Connector supports a plus sign (+) in the ingested SQL queries for dataset expressions. This enables the extraction of connection information from dataset expressions with queries having ‘+’ (plus character) to generate lineage.
Fixed Issues¶
Metadata Extraction Fails for Parameters with Same Name As Table Name in Datasets¶
In Azure Power BI Scanner OCF Connector, MDE fails if a dataset expression has a parameter with the same name as the table name and value as an expression. This is because the length of the object identifier exceeds the limit set by Alation.
November 22, 2023¶
Azure Power BI Scanner OCF Connector: Version 2.1.0¶
Compatible Alation version: 2023.3.2 or higher
Enhancements¶
Support for Cross-System Lineage Between PowerBI and Databricks Unity Catalog, Azure SQL, and Azure Synapse¶
Alation now supports cross-system lineage between PowerBI and the following data sources:
Databricks Unity Catalog
Azure SQL
Azure Synapse
To start using this feature, perform the following:
Upgrade to Alation version 2023.3.2 or later.
Set the following flag to True using alation_conf:
alation_conf alation.resolution.DEV_bi_connector_returns_db_for_two_part_schema -s TrueInstall the latest Azure Power BI Scanner OCF Connector.
For details, see Azure Power BI Scanner OCF Connector.