Michael Steineke on 09 Sep 2015 03:46:32
PowerBI.com should have some type of Source Code control integration for change control
Administrator on 28 Jun 2023 18:23:13
This is now available in preview for Power BI developers.
Check out these resources:
- Deep dive into Power BI Desktop Developer Mode (Preview) | Microsoft Power BI Blog | Microsoft Power BI
- Overview of Fabric git integration - Microsoft Fabric | Microsoft Learn
- Comments (116)
- Merged Idea (7)
RE: source control
Microsoft, please!! Very hard to work with Power BI without GIT integration and CI/CD. The ability to do Pull Request reviews across multiple report developers is essential in this modern world of collaboration.
RE: source control
It would be great to have integration between PowerBI and Azure DevOps for version control. Maybe, Power queries, model and reports separately could be versioned.
RE: source control
It would be great to have version control over a dataflow, such as integration with Github. Sometimes a change can be made to the dataflow logic, which produces an error on refresh and the error detail is relatively poor to assist with identification of the issue. So being able to rollback would be good.
Also, this would allow multiple users to work on a dataflow and ensure the recording of any changes made or even fork if required.
RE: source control
Currently, there is not a way to backup a Power BI dashboard to source control. If the dashboard is corrupted or gets an incorrect change applied, there is not a way to roll back to a previous version.
Please provide an option to allow a copy of the dashboard to be downloaded or connect to a source control option (ie. GitHub, TFS, etc.)
RE: source control
Could we add seamless import/export of the query/data model/measure definitions in text format for use with version control such as GIT?
Right now the queries are all defined as text, tables could be easily defined as field names, field type, and formula for added columns, and measures are just text. Relationships can be exported as a list. This should be 'simple'.
But we also need a seamless import -- import the queries, data model structure, measures from text.
The data wouldn't be part of this as it would be imported by running the queries.
RE: source control
Could we add seamless import/export of the query/data model/measure definitions in text format for use with version control such as GIT?
Right now the queries are all defined as text, tables could be easily defined as field names, field type, and formula for added columns, and measures are just text. Relationships can be exported as a list. This should be 'simple'.
But we also need a seamless import -- import the queries, data model structure, measures from text.
The data wouldn't be part of this as it would be imported by running the queries.