Rajeev Pentyala – Microsoft Power Platform

For the unversed, Using ‘Power BI embedded’ we can embed a Power BI report as Dashboard in Model Driven App.

This Dashboard can be added to a Solution and can be transported to other Environments. However there will be a challenge with report’s Connection reference.

When the Dashboard moved to another Environment, the connection will not be refreshed with Target Environment and will be still pointing to Source Environment.

As an example, if the Power BI report was built connecting to ‘DEV’ Environment, when the report exported from ‘DEV’ using Solution and imported to another Environment, reports connection will be still pointing to the Source Environment (i.e., DEV).

Workaround to refresh the Connection:

• At the time of writing this article, there is no straight forward option to refresh the Power BI report’s Dataverse Connection.
• One option is Save the Power BI report (i.e., .pbx file) locally and create a copy and rename.
  • In my case, I’ve renamed ‘Account_DEV’ to ‘Account_TEST’ file.

• Open the ‘Account_TEST’ file and open the ‘Power Query Editor’ by selecting ‘Transform data’ option.

• From the ‘APPLIED STEPS’, select ‘Source’ and update the Dataverse URL.

• Save the report and publish to Power BI ‘Workspace’

• Assuming you have moved the Report from ‘DEV’ to ‘TEST’ environment using the Solution, as a last step, connect to ‘TEST’ environment and select the report.
• Click ‘Edit’ and select the ‘Account_TEST’ report from ‘TEST’ workspace.

• This manually correcting the report’s connection works. I believe in near future we will have much easier and straightforward approach to refresh conenction.

🙂