SnowConvert AI: Power BI Repointing¶

How to use it¶

1. Locate the Power BI reports in a folder and apply restrictively the extension of a template .pbit.

2. In the SnowConvert AI app, add the path of the Power BI projects in the ETL-BI section.

3. Continue the migration steps as normally.

4. Reports: In the output folder you can review a ETL-BI report about the repointing transformation.

5. Access: In the output folder, you can review the “repointing_output” to access the Power BI repointing reports.

6. Execution: Before opening your reports, it is important to run all your migrated files in your Snowflake account. Otherwise, the object will not be retrieved because they do not exist in the Snowflake account. So, follow the next steps:

   1. Run your migrated queries.

   2. Open your Power BI report.

   3. Add the Power BI parameters required: SF_SERVER_LINK, SF_DB_NAME and SF_WAREHOUSE_NAME. For more information, please review the following Power BI parameters documentation.

   4. Click on load and wait the report to retrieve the information.

   5. Provide your account credential to Power BI app. In the case that you have Two-factor authentication, you may be asked to accept every request of connection from Power BI. Be aware that, there may be several pop-ups for authorization.

   6. Review the ETL-BI report and fix every data entity with issues.

   7. Refresh the data.

Support Insights¶

The current version supports:

• Repointing of tables, view, and embedded SQL queries.

• Maintain the remaining logic steps after the connection steps in the M Language (multiple lines).

• Provides parameters inside Power BI to handle information correctly for Snowflake server link, warehouse and database name.

• Convert queries saved as expression (when “Enable load” property has been disabled).

• Renaming of columns based on related DDLs on the migration or by Power BI report references if DDLs are not provided.

• Identification of views, if related DDLs are provided in the migration.

• Notice that other connections from other sources rather than the selected in the migration settings are not being edited.

Considerations:

• The schema name of the source connections are being used as the schema in the repointed connection. It is assumed that the Snowflake database objects were created under the same schema.

• The database objects must be deployed in Snowflake before trying to open the repointed report.

• If the column renaming step in the M Language is empty, it means that no information was found in the migration context or Power BI project references to create it.

• Functions and procedures are not supported in connectors different from SQL Server and Azure Synapse, so these cases are not supported.

• All found database connections related to the source language in the migration settings will be repointed and parameters will be added.

Troubleshooting¶

• If the user does not enter the requested global parameters after repointing, the load of objects is not triggered by Power BI, so make sure to add the parameter information. If the user clicks on cancel and the reports do not load, then it is recommended to close and reopen the report.

• If a visualization does not load, it may be because a column definition does not match the text case. Notice that the Snowflake connector from Power BI retrieves the entities and columns always in uppercase.

• If you have issues with the credential cache, you can go to settings in Power BI and clear the connection to enter new credentials.

• There may be problems with complex SQL queries after migration. These cases may require extra work to solve warning messages from the migration process (EWI - PRF - FDM).