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.
41 Comments
- '+3 vote for me
- Version control is a must for PowerBI. Some basic version control in the free version, an perhaps some advanced version control in the Pro (perhaps via SharePoint online document libraries? just splitballing here)
- This is a very important feature to position Power BI as a full fledged reporting tool for end users. Else, there would be serious challenge for supporting Power BI reports
- Having version control is essential especially when dealing with a content pack. I agree that being able to tell one version from the other would be of great value to our team. If the report, dashboard or dataset contains the same name, the version number can appear in parenthesis so that users can tell one from the other. Also, if users had the ability to rename the dataset so that the same dataset doesn't appear in duplicate or triplicate would be a great highlight.
- '@Tracy - As you've discovered, changes to reports & dashboards in workspaces are visible immediately. I believe there's basically 2 ways to have more control: (1) One way is thru use of organizational content packs because you choose when to publish new changes (and users have to accept those changes when notified...sidenote: organizational content packs also allow users to personalize their own copy so that's a user training issue because people easily get confused which is the original & which is their personalized version). (2) Make your changes in Power BI Desktop rather than in the service at PowerBI.com. That way you control when the changes are deployed & visible to others. This is more about having a process around where changes are made (because of course there's no way to prevent changes in the service). Good luck with it.
- I posted a question about deleting pending changes and it was suggested that I post to this thread. Below is my post: "I've been looking for a way to not apply the pending changes, but haven't had any luck. Is there an option or way to do this? Any help would be greatly appreciated."
- We need to be able to manage having multiple dev's work on a report together and allow merging versions to combine those changes. Right now all work has to be serialized through a single person that has the golden pbix or pbit file. It would help a lot if the template was exposed as text so that we can manage merging changes and using source control.
- I typically increment version numbers in filenames as I develop on PBI desktop. If I upload my latest report to PBI online, then I have to remove all the existing sheets from my dashboard and pin all the sheets I want from the new report. Would be good if you could point a dashboard at a newer report and pick up all the sheets with the same name.
- It would be great to see Microsoft publish a recommended workflow for this. Like many others, we are currently holding our PBIX files in git as binary files. This gets us close, however there is no way to source control dashboards.
