Skip to main content

Power BI

Under Review

Re-pointing reports/dashboards at different data sources

Vote (247) Share
Nithya Subramaniam's profile image

Nithya Subramaniam on 25 Mar 2015 10:16:45

Ability to build reports/dashboards pointing to a data source (database in the Development / UAT machine) and then use the same reports/dashboards pointing to another data source (in the Production machine.

Comments (36)
Nithya Subramaniam's profile image Profile Picture

d93874c5 ac4c-ea11-a812-000d3a579c39 on 05 Jul 2020 22:22:05

RE: Re-pointing reports/dashboards at different data sources

'@Miguel, that does not work for a Live connection. I need to change the report datasource to use a MD Cube from another environment and this is causing me so much trouble...

Nithya Subramaniam's profile image Profile Picture

a44ecfbd 2c7a-4d29-ab5f-900132f6e683 on 05 Jul 2020 22:17:01

RE: Re-pointing reports/dashboards at different data sources

We need to repoint report as maintenance task and/or during deployment (have single version for all enviroments)

Nithya Subramaniam's profile image Profile Picture

c1d64842 f210-4e95-80ef-8e133c5488b3 on 05 Jul 2020 22:15:37

RE: Re-pointing reports/dashboards at different data sources

Miguel, I have tried to change the database in the Power Query "navigation" option in PBI Desktop on MS SQL databases (on the same server) with database authentication. It doesn't work. Returns incorrect user can't be authenticated despite logon credentials being 100% correct.

Nithya Subramaniam's profile image Profile Picture

08af1352 d3d2-4223-85db-26eb83d4d5f8 on 05 Jul 2020 22:08:34

RE: Re-pointing reports/dashboards at different data sources

So In my world I have Test,Demo and a number of production instances for different clients, each of these environments represents a different Azure databases.
Reading this my understanding was that I would have to start in the desktop environment, Use a Query in the datasource, build up my reports to where I want them. Then to deploy I would save a pbix for each environment.
Then to deploy I would go to each group workspace import the pbix and re apply the credentials for that environment.
Ok, that’s bad, but we are not talking mission critical here, so maybe I can live with it?
But it seems that doing this way, I am unable to have the data updated more than Daily, whereas I could get 15 minutes when I was not using a query but instead a straight Azure database connection.
Is there a way that I can develop and deploy to multiple environments using Azure database as my source and retain the 15 minutes?

Nithya Subramaniam's profile image Profile Picture

e2e6b84b 990f-4200-af5e-4fabe907209c on 05 Jul 2020 21:59:14

RE: Re-pointing reports/dashboards at different data sources

Thanks for the feedback!

You can achieve this today by authoring your reports with either Excel (Power Query, Power Pivot, Power View) or the Power BI Designer. You can access the Source step in your query and reconfigure it to point to a different Server/DB, etc. as the last change to the file before bringing it into the service.

Is that what you're looking for? Any disadvantages with the current solution?

Nithya Subramaniam's profile image Profile Picture

e68f096a 1650-429c-a2a1-d45f45fa3d36 on 05 Jul 2020 21:59:14

RE: Re-pointing reports/dashboards at different data sources

I bring the dashboards (connected to UAT database) to the service, so I can let few end users login to Power BI and check, if the reports are what they want to have. Once they confirm they are ok, then I would want to point to the production database. Currently, I end up rebuilding the reports, since I am not able to re-point to a different data source.