Single Report with Multiple Pages or Multiple Report with One Page

[sulmerj]

I am working on creating a new externally facing Power BI application (Power BI embedded). This application MVP will be comprised of 10 "pages" or "reports" that the users will consume. Is it best practice (eg. best performance, maintenance, etc.) to have one Power BI report with multiple pages for each "report" or one report for each page. Or what are the pros/cons of each option? A team of 3 or 4 developers will be working on this project. The dataset size will be a few GB and will most likely be able to be used across reports (if we go that route). 

Thank you so much in advance!

[Anonymous · Accepted solution]

Hi @sulmerj ,

Thanks for reaching out to us with your problem. Based on your description, it seems like you're trying to figure out the pros and cons of using one report but including multiple pages or using multiple reports. I think this may depend on your situation.

For single report that with multiple pages, if a report has grown to many pages, it might be too much to navigate through. You can apply report-level filters across all pages or sync slicers, use the drill-down feature, and maintain one data model. If you need to change something in the model, you only have to do it once. You can find more details in the following thread.

Solved: Multiple pages vs Multiple Reports - Microsoft Fabric Community

For multiple reports with one page each, if data modelers and report authors are different people, or if a model will be the source for multiple reports, now or in the future, it makes sense to separate model and report development into separate Power BI Desktop files. It is usually more usable to separate report files with fewer pages targeted towards specific needs...

Separate reports from models in Power BI Desktop - Power BI | Microsoft Learn

5 Tips for Separating Power BI Datasets and Reports — Coates Data Strategies

Best Regards