Many Power BI developers have experienced the frustration of learning that a report that they’ve developed is no longer working. Upon investigation they learn that other people have made enhancements to this report and somewhere along the timeline, things have fallen off the rails.
Today’s reality is that Power BI does little to help you compare changes across versions, or indicate “who made what change when?”
This is a reality because the pbix file format makes it difficult to see the code stored in the file for the various report components, conversely, making it difficult to track changes across versions or a Power BI Report.
Don’t be discouraged – All is not lost – A solution exists!
Git and pbi-tools to the rescue!
We can leverage Git [a free, open-source version control system (VCS)], to provide the ability to track changes over time.
Git then leverages pbi-tools to make sense of the contents for the pbix file format.
In this session we will demonstrate setting up and integrating git with pbi-tools to achieve change tracking across Power BI Report versions.
I will also demonstrate how developers can ‘commit’ changes to git, make changes over time, and then highlight the differences in code across versions. This capability to Track Changes allows developers to resolve issues quicker and have greater insight on what is changing in their reporting solutions.
During this session we will also talk about the history of Version Control options Power BI, we will also look at a free new community beta tool from the Tabular Tools, PBIExplorer, which might be a future solution for looking at changes in the Power BI Reports.
Sign up to stay up to date with news, special announcements and educational content.
Redgate will only contact you about PASS Data Community Summit (in line with our Privacy Policy) unless you separately request emails about Redgate. You can unsubscribe from these updates at any time.
Summit video library