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
Integrated source control and diff is critical to consider this a professional tool for enterprise.
RE: source control
I'm a little surprised no one from the MS has chimed in here
RE: source control
This is a serious issue for us and will block widescale adoption of PowerBI across our 300 strong team.
Is there any progress on this?
RE: source control
Any updates on if this is a road map item? This would be fantastic, as some other people have pointed out powerbi-vcs on github is a temporary unofficial solution..
RE: source control
It would be great to be able to use GIT and /or Visual Studio Team Services to source control the development of Power BI solutions...
RE: source control
This currently works for 'proper' version control (i.e. merges/diffs/etc.): https://github.com/kodonnell/powerbi-vcs . The UI hasn't been started and it's not battle-tested, but it has worked on what I've tried so far. Feel free to submit some PRs!
RE: source control
We need a few things - version control in tfs, ability to diff, edit code behind during a merge in order for Power BI to scale at enterprise level.
RE: source control
Technically there is source control with #PowerBI if you have #Office365. If you create a workgroup, which is best practice for a corporate environment, a Sharepoint site is created for the group, which has things like check in, check out and versioning. No merging though, which I would like. Here's a link for more information http://wp.me/p4beUo-nU
RE: source control
Same thoughts here. Integration with source control must be possible, regardless if Power BI is used as "self-service" or for formal development.
RE: source control
Even though Power BI is marketed as a "self-service" tool rather than a developer tool there are no doubt many formal developments being undertaken with it. Therefore, hopefully Microsoft will include some developer friendly functionality,
Would be good to be able to point it to an existing TFS project and then create a new project to hold pbix files so that you can keep all artefacts (e.g. table scripts, stored procedures, SSIS jobs etc) in the one place. An auto commit option upon publishing a report would be good too.
Would also be cool if reports could be viewed (if not edited) within Visual Studio. The ability to edit reports using VS would make PowerBI more consistent with other microsft BI tools.