Forum Discussion
Power Bi report deployment to Production:
We are good with Dev server and all pbix reports validated. Now how to move these reports from Dev to Prod?
I am not able to edit the data source connection string under manage —>data sources. Am only able to edit the connection permissions.
So how to edit the connection string to point to Prod data sources?
It’s not an ideal solution to open in desktop application and then edit connection and deploying to Prod. Once it’s signed off in Lower environment I can’t change the pbix file at any cost.
Please suggest what are the best ways for changing data sources of pbix file.
Thanks
Manoj
- Anonymous7 years ago
You can GET and PATCH the data sources for a deployed PBIX using the REST API /PowerBIReports({Id})/DataSources
As you say there's nothing in the SSRS PowerShell library to support this directly. You would need to create your own function/code.
There are various examples kicking around
http://byobi.com/2018/04/programmatically-deploy-power-bi-reports-to-power-bi-report-server/
This one shows how to use the powershell modules though the way they adjust connection strings in the dat asource sound **bleep** scary to me.
https://www.blue-granite.com/blog/power-bi-report-server-devops
regards
Steve
6 Replies
- HeitorSantosRegular VisitorI'm having the same issue.
Does anyone knows a solution?- AnonymousNot applicable
Need to accept the limitaions. Yes.
But at Enterprise level, making a modification to a pbix file (after it is signed off in UAT) is not acceptable.
Please suggest if there is any alternate solutions.
Thanks
Manoj
- AnonymousNot applicable
You may have to use the REST-APi for PBI-SSRS. Details are here https://app.swaggerhub.com/apis/microsoft-rs/PBIRS/2.0
You can use these via the PowerShell library https://www.powershellgallery.com/packages/ReportingServicesTools/0.0.4.7
You could write yourself a script and pass in the path to the report you want to transfer. It could download the pbix and then upload it. This way you are transferring the object as is. You would need to trap if you are creating it or over-writing it on the destination. You may also need to do some work around security, we use folders so the security is applied to the folder and the reports just inherit the securty for the folder they are deployed in so we don't have to sorry bout this sort of stuff. We deploy from version control not from another server however.