Michael Steineke on 09 Sep 2015 03:46:32
PowerBI.com should have some type of Source Code control integration for change control
- Comments (66)
RE: source control
We keep the pbix files in Bitbucket, but it's impossible to see what had changed with it being a binary file. We have to keep manual records for release info. One of the main reasons for Source Control is to have visibility of what changed, it's no longer just about keeping the previous version(s) if something goes wrong.
RE: source control
I would love to open within Visual Studio and have GIT or TFS as version control
RE: source control
A team experienced with SSRS and SSDT in Visual Studio will continue to have difficulties adopting Power BI (and especially Power BI Report Server) without some support for standard source control practices. At the very least we need a Visual Studio plug-in that either integrates Power BI Desktop components into Visual Studio, or one that connects Visual Studio more tightly with Power BI Desktop. Even if we can't diff the files, at least making the templates and frameworks for PBI reports behave more like SSRS reports would help. Or...finish integrating paginated reporting within Power BI Desktop and expand the toolsets from there.
RE: source control
Please ensure that the for mat allows for text diffs. I might also ask that code be separated from visual items in the format so that I can easy see different calculation changes. Very important for auditing of financial reports.
RE: source control
Can we integrate Power Bi with BitBucket
RE: source control
This should also work for PowerBi for Reporting Services
RE: source control
Isn't this already in DevOps https://msftplayground.com/2018/12/administrating-and-publishing-power-bi-resources-via-azure-devops/
RE: source control
There's a potential solution in this idea too https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/36978934-built-in-git-support-in-powerbi-desktop
RE: source control
this is basic need for professional development work
RE: source control
If Microsoft made PowerBI Template (.pbit) files more flexible, i.e.:
1) capability to export a .pbit from PowerBI Report Server (and cloud)
2) OR capability to export a .pbit by command line from a .pbix, preferably PowerShell so it does not depend on the PowerBI Desktop .exe
3) capability to upload a .pbit to PowerBI Report Server (and cloud)
then some of the deployment automation could be completed by the community which has done of some this work already
Git-LFS has been an interesting solution as well, but I think is ultimately just a crutch for the main problem here in that the file format is inflexible