on 10/18/2022 12:57:10 AM
Update 10/17: This is now in our upcoming roadmap and we will share more details in the coming months. Mo
March 2022 update: We are looking into this but we dont have a timeline as of yet
This really required feature for any type of license we hold (Pro or PPU or Premium Capacity). For Microsoft I don't think it is big deal to achieve.
we are consuming a Tabular cube, live, through PowerBI. The PBIX files we have are tiny -- it would be nice to source control the reports/dashboards metadata.
thank you --
Yes, Do this!!
Requesting for this feature. Hopefully this gets added to the roadmap soon.
Please do not limit this to only Premium Licenses.
We are starting to implement some basic source control on pbix report files that are separated from the dataset. We are ready for source control at any level. Of course we want version control integrated with the pbi service for dataflows and datasets too.
Microsoft, please implement this, it is critical for effective collaboration on reports, we really need this.
This issue just came up again today. Clearly, this needs to be implemented, since it's difficult to ensure there's a copy of the previous dashboard version as part of the publication process. This needs to be prioritized ASAP.
Why is this still in 'Needs votes'. This is clearly something that should be on your backlog asap.
Has anyone else been around long enough to remember "CAB" files in SQL Server 2000 Analysis Services? That was where analysis services metadata was kept. The "CAB" was similar to a pbix, in that it was a very annoying binary file that was difficult to manage in source control... My memory is fuzzy but there was a utility, that could be pointed at a deployed version of the OLAP database and it would generate AMO script which was theoretically a text-oriented representation of the CAB's contents.
The pbix files for Power BI seem very similar to the old CAB files. Only this time around Microsoft hasn't give us any utility to extract the contents of the binary. So there is nothing we can add into source control for diffs (change tracking).
It is interesting how you can take so many steps forward, just to find you've come full circle!
I work at a large enterprise >5000 employees, and the lack of source control for .PBIX files and Power Query M scripts is by far the main reason many employees do not seem to take Power BI and Power Query seriously at my organization compared to pure programming languages for data analysis like R. Power BI and Power Query team. If you guys would FINALLY implement source control, Power BI and Power Query power users like myself would finally be able to overcome this huge cultural barrier and scale PBI/PQ solutions within the enterprise. As is stands, many employees view PBI and PQ as child's play and a recipe for chaos and impossible to collaborate on since it has no source control integration