This article describes how to migrate and existing Excel or Power BI reports from the on-prem data warehouse (BPW) to the cloud data warehouse.
Changing the Data Source
- Open the existing Power Query file and click on Data->Get Data->Data source settings
2. Select the connection 'bpw.kemin.com' or 'uskibpw3.kemin.com', then select Change Source.
3. Enter the following connection information:
Server: sqlmgi-dw-dev.2e65a4975724.database.windows.net
Database: sql-mgi-dwh-datamarts
Please note this parameters are only valid for TRN environment. To connect to PRD environment we'll have to use different parameters that will be shared after full scale testing.
4. click OK and then Click Edit Permissions.
5. Select Microsoft account then Sign in.
6. Click on your account.
7. Then Select Save.
8. If you see the below message about Encryption support. Click OK.
9. Click on OK then Close.
10. Select Refresh All in the dropdown menu of Refresh Preview to update all queries.
11. Review each query in the Queries list to ensure that they are not returning empty tables or errors. The following section addresses the most common error cases and proposes solutions.
12. Once all errors are resolved. Click on Close & Load.
Troubleshooting
Case 1: Table names have changed
If you encounter the above error message, it indicates that the table has been renamed in the cloud.
To resolve this issue, please click on the gear icon of the Navigation step. Thereafter, select the corresponding table and click Save.
If you are unsure which is the correct table to connect to, please refer to this Lineage on Cloud Data warehouse report, or open a Help desk ticket.
Case 2: Column names have changed
The error message above indicates that the column name has changed in the cloud.
To troubleshoot, locate the first step where this error message starts occurring and change the column name in the formula bar instead of using the gear icon to avoid missing other renamed columns.
To find out the new column name, go back to the navigation step and check the list of all available columns.
Case 3: Filtered value no longer exists in cloud
The message above usually indicates that a filter applied is filtering on values that does not exist in cloud. The most common examples are filters applied on columns related division, facility, warehouse, order type, or dates.
To troubleshoot, simply update the filters. First locate the applied step, the click on the gear icon to change the values.