7 Merged Ideas
Comments Provide the ability to have source control against PBIX development in order to manage releases etc
Power BI Desktop or Service does not support BI Life Cycle Management. Therefore could Visual Studio Team Services be used for Dashboard, Report & Dataset version control.
Automatic versioning and the ability to create branches of queries to allow parallel development and better version history.
PowerBI.com should have some type of Source Code control integration for change control
In order to be a legitimate software tool all parts Power BI really needs to be persisted in some text format that can be diffed and changes reviewed and approved. Otherwise we are stuck in the binary dark ages!
Please.... Otherwise we end up creating convoluted processes. Personally I think SharePoint\OneDrive is perfect for tracking versions. One click to save and open. I don't want to find out how many it takes to work with Github.
Having Power BI integrated to DevOps CI/CD pipelines can be of a huge leverage for the Power BI evangelizers to implement the Power BI full-blown in businesses.
Although you can already 'do version control' by linking a SharePoint library, I would opt for Git integration, and not just 'any kind of source control'. Or more specifically, not SharePoint, as versioning is not the same as source control!
It would be really great with integration of PowerBI into Azure Devops or GitHub. Also, more transparency on the elements of a .pbix file, and the possibility to open, edit, and pull/push changes. We really need this!
Please, please, please come up with a solution for source control. Need this sooner, rather than later.
Thanks!
Angie
Administrator 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