Power BI Best Practices - Part Three

Overview

In this article, we will talk about the best practices to be considered while we are working with Power BI Report development. I have divided the best practices into the following three parts. This is the last article in this series. Please visit my other articles of this series using the following URL,

During the entire series of the best practices, we have covered the following concepts.

  • Best Practices for Power BI (. PBIX) file preparation (Part – 1)
  • Best Practices for Power BI (. PBIX) Properties (Part – 1)
  • Best Practices to use Query Editors (Part – 1)
  • Best Practices for Tables and Relationship (Part – 2)
  • Best Practices for creating Calculated Columns, measures, and Fields (Part – 2)
  • Best Practices for Data Analytical Expressions (Part – 2)
  • How to make Documentation within PBIX file (Part – 3)
  • Best Practices for Power BI Report Design (Part – 3)

In this article, we will talk about the following concepts for the best practices.

  • How to make Documentation within PBIX file
  • Best Practices for Power BI Report Design

Let’s get started!

How to make Documentation within PBIX file

  • Document the Solution File

    • This is a very good practice, we suggest to our clients.

    • We recommend having a first or last page in a report which has following information about the report.

      • Owner Name
      • Data Source Information
      • Consumed Table List
      • Important Definitions/Terms used in the data source
      • Useful Measures Information

    • Make sure before you publish the report on Production, that you hide the page.

    • This is only for a development perspective.

  • Descriptions for Fields

    • Add a proper description of Fields, Calculated Columns and Measures.

  • Comments in DAX Calculations and M Query

    • We also recommend using comments in every DAX expression.
    • This would be helpful for others to understand the logic or calculation.
    • We have not observed if any M query is used in the report or not.

  • Rename the Query Steps

    • Steps which are added in the query editor are auto-named.
    • We recommend renaming it for a better understanding of the other users.

Best Practices for Power BI Report Design

We follow the following best practices while designing for any corporate audience.
  • Company Logo

    • Use the Logo in their background.

  • Data Timestamp to show, when it was refreshed last

    • We can implement it, to show the end user, when the data was refreshed last.

  • Less use of scrollable Page

    • End users always feel difficulty when the report has a scrollable page.
    • We do not recommend making the page scrollable if not necessary.
    • Instead of making page scrollable, use Bookmark and Selection Pane.
    • Census dashboard doesn’t have a scrollable page which is good.

  • Use Basic Reporting Filter

    • Power BI provides the following type of filters.

      • Visual Level
      • Page Level
      • Report Level

    • Use the filters wisely as peryour  requirement.

  • Limit the number of visuals in the report

    • If we place so many visuals on the single page, it will slow down the performance.
    • We recommend using a maximum of eight visuals per page.
    • Sometimes, based on requirement we need to add more visual on the page, at that time we need to prioritize and choose visualization wisely.

  • Remove unnecessary interaction to improve the Performance

    • By default, interaction is added to every visualization.
    • We recommend turning off the interaction if it is not needed which will improve the report performance.

  • Use Certified Custom visuals

    • If the organization is planning to use any custom visuals in future, make sure it is certified.
    • Certified custom visual is the custom visual which facilities the functionality to be exported to PowerPoint and email subscription.
    • To know more about the certified custom visualization, please refer to the following here.

  • Do not use Hierarchical Slicers

    • We recommend, not to use any hierarchical slicers in the report.
    • Currently, we have observed that no hierarchical slicers are used in the report.

  • Also, before planning any report development, we will consider the following points

    • First, we think about the data in Grid
    • We use proper suitable charts which represent the data in an effective manner.
    • Use the proper color scheme.
    • Do not mess up, make it simple.
    • Use simple titles and headers.

Conclusion

This is how we recommend the best practice to prepare the Power BI report. Hope you love this article. Stay connected with me for more amazing articles!