Microsoft on-premises server product that runs Office Online.
Dear John Bazenas,
I understand your concern. As a starting point, I recommend following the guidance in the AI answer above, as it covers several of the most effective ways to reduce the amount of data processed by Power BI Report Builder.
In particular, consider filtering the dataset or query so only the required records are returned, using report parameters to limit the data users can request, and removing any unnecessary columns or rows. If the report only requires summary information, grouping or aggregating the data instead of returning detailed records can significantly reduce the dataset size.
- Also keep in mind that paginated report visuals have data reduction limits. If your report exceeds those limits, filtering the data earlier in the query and narrowing the report scope can help prevent rows from being dropped or performance issues from occurring. For reference: Create and use the paginated report visual
- If the report is based on a Power BI semantic model, you might also consider limiting the number of rows displayed by using a Top N filter or by designing the report so users first view summary data and then drill through to details as needed. This can significantly reduce memory consumption and improve performance without affecting the user experience. For reference: Apply the most restrictive filters
Since this forum is primarily focused on Microsoft 365 products and services, Power BI-specific questions are often best handled by the experts in the Microsoft Fabric Community. Therefore, for further recommendations, you can post your questions and receive more specialized assistance in the Microsoft Fabric Community, which is dedicated to Power BI, Power BI Report Builder, paginated reports, and related data platform products.
Here's the Microsoft Fabric Community (Power BI) site: https://community.fabric.microsoft.com/category/powerbi
If you have any questions or if I have misunderstood anything, please feel free to reach out.