on 3/18/2022 4:21:25 AM
March 2022 update: We are looking into this but we dont have a timeline as of yet
It is quite paint not to be able to compare changes between 2 versions of PBI file - since the structure is not readable by normal text editors :-/
Also it prevents 2 users to be able to make changes to same file at the same time.
We are using Visual Studio and Team Foundation Server to keep our published versions of reports clean, but we cannot really track any changes within file itself.
Source control should become a standard within Power BI.
I am still not believing this function got 0 attention so far, a must need for corporate and big teams!
Even a simple per-user "locking" mechanism would be a big first step. A very typical workflow is: (a) download report as PBIX from service (b) make changes in PBI desktop (c) publish. Without a lock very problematic even with a small number of contributors.
We are several team members contributing to a Power BI project and having source code control integration would bring a major improvement.
PowerBI really needs to connect to TFS for source control as SSRS currently does.
Source control is both needed for our daily work and will help enable the same PBI Template to point at our different databases.
Integrated source control and diff is critical to consider this a professional tool for enterprise.
I'm a little surprised no one from the MS has chimed in here
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?