Dataset/Report Version Control

[SnoJa10]

Currently, I can upload an Excel file with Power View reports and the data behind it. This is great, but the file cannot have any version control. I would need to be able to continue developing my reports through version control and then point Power BI to the updated dataset/report without having to re-upload and create everything from scratch. This becomes absolutely essential when you consider dev/production environments. We can't expect to provide users with cool new dashboards, then a week later take it down because there is a newer version.

[Harvey_Randhawa]

This is a great idea

[Elizabeth_Hunt]

Yes, we need to be able to comment on deployments.

[straitm]

This is immensely needed. This will add so much value to the deployment pipelines. Get this in place and Power BI will crush any other BI tool competitor. Rollback and Version Control inside of the Power BI service with a Deployment Pipelines. Just saying that sentence makes me giddy with excitement. The adoption of the product would just continue and it will bring a bit more respect to the developers. Right now the version control aspect with the Power BI service is a bit weak and scary. We use Azure DevOps to check .rdl's and .pbix files in and such. But have Rollback and version control attached to a Deployment Pipeline within the Power BI Service would be invaluable.

[nishalit]

Featuring power bi version control activation, may potentially easy track dashboards composure and history. Not featuring power BI version control, user my not easily visually identify power bi dashboard composure history tracking. Alternative, the user could create multiple files or dashboards, or pages of dashboards.

[nishalit]

Vote on this idea if you want a functionality to enable Version Control on reports in Power BI Service and version control on comments applied to reports. Also, It would be nice to have an automatic backup of the published reports in the Power BI Service workspace.

[nishalit]

The deployment pipelines seem to be a great way of operationalizing BI development. It would be awesome to have some kind of version control (e.g., Git) behind the scenes to which you can commit and thus push up to the next stage. Then we can have history for everything, rollback, commit messages, documentation etc.

[nishalit]

There would be a great idea if you can add feature of Rollback the Report to the previous version if let say the Deployment did not go well. Also, would be great if we can have reports version history.

[andrew_manlutac]

A great feature for powerbi online service (dataflow,dataset, or datamart) would be to automatically cancel a scheduled data refresh if it fails AND revert back to using the last successful data refresh so there is less impact to end-users/consumer. The goal would be to reduce the likelihood that powerbi visuals/reports would still work even if the data refresh fails because it would always keep the same data from the most recent successful refresh even if a failure occurred. This could be similar to how windows has a system restore to the last point the system was working well. If we could have this feature it would allow for more control over the data to ensure users get the most accurate information during a failure.

[Quazar_Partingt]

As part of the version control, some level of Difference Detection would preferred.

[nicholas_hoffma]

Please add diff capability + version control.

I'm manually doing this by saving out query and measure M-code / DAX to text files which I then manage in git..... this works, but is a huge time sink.