The new release of Power BI Documenter provides lots of new information about your Power BI reports along with one more best practice.
We’re excited to announce that Power BI Documenter V2.75 (October 2018) has been released for public use. The new release of Power BI Documenter provides lots of new information about your Power BI reports along with one more best practice. In this release we fixed some bugs and added bunch of new features as follows.
Fixed bugs in the new release?
We have noticed a minor bug in “Model Details” data grid under “Model” tab which the “Field” column resized vertically and made it pretty hard to read the text.
We fixed the issue so the “Filed” text will not resize in a way that makes the text unreadable.
We also notified with an issue in the sorting files in the “Files” page. In this release we fixed that issue and from now on your files will be in descending order based on uploaded date.
What is new in October 2018 release?
Power BI Documenter 2.75 comes with a bunch of amazing new features that can help you with your Power BI development as well as documenting your Power BI reports.
Supporting built-in themes
Detecting unused custom visuals and providing relevant Best Practice
Detecting Mobile Friendly reports and visuals
Row Level Security (RLS)
Report Level Measures when Connect Live to an instance of SSAS
Supporting built-in Themes
Built-in Themes made available in Power BI Desktop from August 2018. From now on Power BI Documenter detects if a “Built-in” theme has been used in the Power BI reports.
Detecting unused custom visuals
The ability to use custom visuals is awesome. They can take your reports to the whole another level. They are shiny, informative and more importantly, easy to import to your reports. No scripting is needed, you just need to import any desired custom visual to your Power BI report to be able to use them. But, in reality you may import several custom visuals to see how they work. You may use some, but what about the unused ones? You may simply forget to remove them from your model. The problem with unused custom visuals is that they still consume some space in your Power BI report which make your PBIX and PBIT files larger. This release of Power BI Documenter can detect unused custom visuals so you will immediately identify unused ones in your report which perhaps you’d like to remove them as soon as you can. To see which custom visuals are not used in your report, after uploading your PBIT file to Power BI Documenter, click on “Custom Visuals” tab.
Best Practice on Unused Custom Visuals
We added a new best practice about unused custom visuals. If you have at least one unused custom visual you will see the following message under “Practices” tab in “Unused Custom Visuals” dropdown:
Otherwise you see the following green tick:
Detecting mobile friendly reports and visuals
One of the features available in Power BI that is loved by the end users and customers is “Mobile Friendly” reports. You can easily make wonderful reports that can be easily used on virtually any mobile devices. But, when it comes to Power BI documentation and handover, it is really hard to go through every single report page, switch to “Phone Layout” and see which visuals are used in mobile friendly mode. Using Power BI Documenter you save heaps of time on identifying mobile friendly reports and visuals. All you need to do is to upload your PBIT file to Power BI Documenter then under “Report” page you’ll see icon if a Phone Layout is available for the report pages and if visuals are used in the Phone Layout.
Row Level Security (RLS)
The October 2018 release of Power BI Documenter supports “Row Level Security (RLS)”. So from now on you’ll get your RLS settings documented after uploading your PBIT file to Power BI Documenter. Then click on a new “Roles” tab added to the Documenter. You can simply expand the dropdown to see the expressions used in the RLS.
Report level measures when Connect Live to an instance of SSAS
One of the coolest features of Power BI Desktop is the ability of creating Report Level Measures when connecting live to an instance of SSAS Tabular. This features opens the doors to SSAS Tabular development team to work more closely with Power BI developers in an enterprise scale project. The way it works out is that Power BI developers can create new measures in their Power BI reports when needed. So they don’t need to wait for the SSAS Tabular developers to create the measures and deploy the solution to make the measures available for Power BI developers. As a matter of fact, after the Power BI developers create the Report Level Measures in Power BI, they can simply handover the DAX expressions to SSAS Developers to use those expressions to create the measures in Tabular model. Currently, in Power BI Desktop, there is no easy way to identify the Report Level Measures. It can get a serious problem when you open a Power BI Desktop that someone else developed and you need to identify Report Level Measures. The only way in Power BI Desktop is to click on every single measure in the “Fields” pane and see if any expressions show up in the expression box. Imagine if you have a Power BI report connected to a Tabular model with hundreds of measures and you need to find out which measure is actually a Report Level Measure; that can be a real nightmare.
We at Data Vizioner identified this time-consuming process and we are excited to make this feature available in October 2018 release of Power BI Documenter. So from now on, you can simply upload your PBIT file to Power BI Documenter with a simple click, then go to “Model” tab and you can see full information about the “Report Level Measures” and their DAX expressions. We didn’t stop there, in the “Model” page we give you full information about the measure usage in Report Pages and Visuals.
LEADING DATA INTELLIGENCE PLATFORM
Enhance governance, accelerate analysis and automate documentation with a single data intelligence platform.