network file share), then the limitations on functionality for published reports mentioned above do not apply. Many users will feel more at ease with Excel than with any other tool. This is an important factor that should not be ignored. Best Practices for Report Design in Power BI Desktop It is beyond the scope of this whitepaper to go into detail on best practices for report design in Power BI Desktop. Entire books have been written on the subject of creating and optimizing DAX calculations, for example. However, it is possible to offer some simple tips and tricks that will make your reports as responsive and easy to manage as possible. Managing Report Authorship Controls over who builds reports, where these reports are published, and how many reports are published, are essential if you are going to avoid thorny issues later on in your project. If you allow unrestricted report authorship you will find that duplicate reports and datasets are created, and this in turn means that: Maintenance of reports becomes time-consuming and difficult, for example when data sources change or calculations need to be altered. You reach the limits for how much data a user can publish using a Power BI Pro subscription, or even the available memory of your Power BI Premium capacity, more quickly. Scheduled refresh for large numbers of reports at the same time can put excess load on data sources, making both the data sources and the report refresh slow. Different data modeling decisions, variations in how calculations are defined, and even inconsistent column and measure names, mean that users have difficulty comparing the data displayed in different reports and are unsure which reports to trust. This is not a recommendation to centralize all report authorship in Many of these the IT department because that diminishes many of the beneficial considerations relate aspects of self-service BI. However, it is important to ensure that: more to the ‘process’ All report authors are properly trained. and ‘people’ side of the Report authors follow your organization’s documented equation, rather than best practices and standards when building reports. ‘technology.’ The Duplicate reports and datasets are avoided. whitepaper discusses Reports are thoroughly tested before they are published. many of these aspects. Reports always have owners who are responsible for maintaining them, and answering questions, after they have been published.
network file share), then the limitations on functionality for published reports mentioned above do not apply. Many users will feel more at ease with Excel than with any other tool. This is an important factor that should not be ignored. Best Practices for Report Design in Power BI Desktop It is beyond the scope of this whitepaper to go into detail on best practices for report design in Power BI Desktop. Entire books have been written on the subject of creating and optimizing DAX calculations, for example. However, it is possible to offer some simple tips and tricks that will make your reports as responsive and easy to manage as possible. Managing Report Authorship Controls over who builds reports, where these reports are published, and how many reports are published, are essential if you are going to avoid thorny issues later on in your project. If you allow unrestricted report authorship you will find that duplicate reports and datasets are created, and this in turn means that: Maintenance of reports becomes time-consuming and difficult, for example when data sources change or calculations need to be altered. You reach the limits for how much data a user can publish using a Power BI Pro subscription, or even the available memory of your Power BI Premium capacity, more quickly. Scheduled refresh for large numbers of reports at the same time can put excess load on data sources, making both the data sources and the report refresh slow. Different data modeling decisions, variations in how calculations are defined, and even inconsistent column and measure names, mean that users have difficulty comparing the data displayed in different reports and are unsure which reports to trust. This is not a recommendation to centralize all report authorship in the IT department because that diminishes many of the beneficial aspects of self-service BI. However, it is important to ensure that: All report authors are properly trained. Report authors follow your organization’s documented best practices and standards when building reports. Duplicate reports and datasets are avoided. Reports are thoroughly tested before they are published. Reports always have owners who are responsible for maintaining them, and answering questions, after they have been published. Many of these considerations relate more to the ‘process’ and ‘people’ side of the equation, rather than ‘technology.’ The whitepaper discusses many of these aspects.
Planning%20a%20Power%20BI%20Enterprise%20Deployment.docx