Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowJuly 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more
In the past, with PBIX files I have managed version control of Power BI in one of two ways.
1. Save the datasets as templates to remove the data and then include the datasets and reports as part of the Visual Studio solution so it is captured as part of the Azure DevOps GIT repo.
2. Use a storage account to either manually capture versions or as a backend for Power Automate and Power Apps to store versions.
Question is.
With Data Flows and now the recently released Data Marts, these are built in the portal so how do you version control these?
If you can export the JSON, and re-import it if needed that would probally be the easiest option. Asuming you can re-import it to roll back?
For dataflows, I export the json from the service, and place that in git
I haven't looked at the datamarts yet
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
Join Fabric Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.
| User | Count |
|---|---|
| 15 | |
| 14 | |
| 12 | |
| 11 | |
| 8 |
| User | Count |
|---|---|
| 40 | |
| 36 | |
| 29 | |
| 27 | |
| 24 |