1726
PowerBI.com should have some type of Source Code control integration for change control
STATUS DETAILS
Planned

 March 2022 update: We are looking into this but we dont have a timeline as of yet

Comments

M

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..

M

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...

M

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!

M

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!

M

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.

M

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

M

Same thoughts here. Integration with source control must be possible, regardless if Power BI is used as "self-service" or for formal development.

M

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.

M

We currently use QlikView as our BI platform, which integrates (indirectly through SVN) with GitHub. QlikView reports (QVW's) are broken down into a series of XML and text files, and a single binary file. It would be nice to have a solution like this for easy integration with any source control system.

M

'Here's my dream workflow:
1. My developer creates (on their own computer) a new BI chart that displays my data just the way I want it
2. They "publish" to the web and the source code goes with it
3. Enjoy the awesomeness of PowerBI on the web!

-------- time passes

4. I tell a different developer to update the chart
5. They download the source code from the web, right where it was published!
6. They update chart and when they publish, the new code is saved to the web!

Right now my team has actually lost source code to a chart, requiring us to recreate the chart from memory. This was because we didn't even think that the source code wouldn't be saved