Vote for Change For Support of Source Management and CI/CD of Power BI Reports
Our team has implemented change management for some critical Power BI Reports used by other teams at my company. We do this by extracting the “.pbix” zip file that makes up a report and storing the individual files into Perforce. We use an internal Perforce-integrated system for tracking changes to the report and, most helpfully, for deploying the changes made on our development system to our test and production systems. One issue that we have is the size of the data part of the “pbix” versions of the reports. A file named “DataSource” holds the report’s data at the time the “.pbix” file was last saved with Power BI Desktop. This file can get very large. We have reports whose “DataSource” files contain almost 200 MB of binary data. It’s not a good idea to put these into source file systems made for smaller text-based files, especially since tracking differences between versions of these data files is not useful nor often even possible. Power BI Report Desktop provides a way to save reports as “.pbit” templates. These are also zip files that are nearly identical to the “.pbix” files and would be a better alternative for change management. They have the benefit of replacing the large “DataSource” file with a much smaller text file named “DataModelSchema”. This smaller file appears to have enough information (specs of the data source connection, names of tables, names of columns from the tables, etc.) to be able to recreate the “DataSource” file. Currently however, the only way to do this “re-creation” and produce a publishable version of a report from a “.pbit” template is for a human to use Power BI Desktop to “Save As” a “.pbix” file. This “.pbix” file can then be uploaded to the report server or saved directly to the report server. (This is also the only way to do this with the new, somewhat promising “.pbip” files currently in preview, see link below). Having a script that replaces the manual Power BI Desktop “Save As” step or at least recreates the “DataSource” would be ideal for inclusion in an automated report deployment process. Unfortunately, I have not been able to find such a script from Microsoft after exploring multiple support sites. I’ve since had a call with Microsoft support and they’ve confirmed that there is currently no way to do this conversion automatically. What I did find in my online searches was an MS support response that included a link to this page where interested parties can vote up a feature that would address this issue: https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=e41d996b-1fc4-463a-b8ab-bdedb73728d3&page=8 I also confirmed with Microsoft support that getting this feature many votes increases the likelihood that it will be implemented in a future version of Power BI. I ask readers of this post to spread the word to fellow Power BI Report users and organizations who would benefit from this proposed feature…and please ask them to vote up the idea. 😊 Thank you. P.S. Here is a link to the potentially promising new file format for Power BI Reports: Power BI Reports Projects: https://learn.microsoft.com/en-us/power-bi/developer/projects/projects-overview
Change Datasource In report
Hello, I developed a report in a development environment, whose data comes from a local SQL server. The report has to be deployed on a production environment pointing to the corresponding production SQL server... However, once deployed on the power bi report server, it is not possible to adapt the server name, impossible to change the data source! and it is not possible to do it from the development environment because the production SQL server is not accessible from the development environment. How to do it? Thanks, Regards, Hervé