James Snowball on 07 May 2015 18:53:31
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.
- Comments (29)
RE: Dataset/Report Version Control
What I really need is to delete pending changes. You must rebuild the file if the pending changes mess it up.
RE: Dataset/Report Version Control
If you are using SharePoint online and Teams then creating a version control team in Teams and copying in (not deleting and reuploading) means that when you view on SharePoint it has the full version history of the updates you have made, a simple excel sheet with what the changes ensures that you know what save has what changes.
RE: Dataset/Report Version Control
Should combine this idea with the idea with 1.2k+ votes: https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/36978934-built-in-git-support-in-powerbi-desktop
RE: Dataset/Report Version Control
Change management and version control is pure chaos without this feature. The data and binary info needs to be separated from the DAX/Dataset Queries/Visualization attributes/etc such that merge/diff would be enabled and the latter should be able to be source controlled via GitHub/GitLab/etc. Sorely needed for collaborative teams!
RE: Dataset/Report Version Control
My idea is a "Team explorer" version control window in PowerBI
This would require the ability to export the report (no data, no Power Query*) from the Power BI file as it's own git friendly file type. This would then allow full version control.
It may also require a "dataset" included template. Which would be a everything in the current template method, but git friendly format.
*like a PowerBi report that connects to a data set in PowerBi service.
RE: Dataset/Report Version Control
Specifically, make it possible to export all of the settings for a Power BI file into a set of text file. Include each query's advanced editor code in a text file. Include each measure and column into a text file. Include each visual's filters, fields, formatting, and analytics in a format like json. It'd be nice to have a way to measure the exact differences between two different versions of the same Power BI report using a text file difference tool, or be able to produce a Power BI report with exact specs given by a text file.
RE: Dataset/Report Version Control
I am shocked that any development tool in 2019 doesn't support proper version control. This is the #1 feature PowerBI needs right now, ahead of any additional data tools.
RE: Dataset/Report Version Control
Potential solution in this idea https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/36978934-built-in-git-support-in-powerbi-desktop
RE: Dataset/Report Version Control
There's a potential solution in this idea too https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/36978934-built-in-git-support-in-powerbi-desktop
RE: Dataset/Report Version Control
We need ability to compare versions, both in git and TFVC.