Forum Discussion
Paginated Report Matrix with Dynamic Columns Causing PDF Export Issues
Hi everyone,
I'm working on a Paginated Report (RDL) that contains a matrix. The matrix columns are grouped by Product Type, so the number of columns grows dynamically depending on the data returned.
Scenario
- Rows contain summary data.
- Columns are grouped by Product Type.
- The number of Product Types varies and can become quite large.
- As more Product Types are returned, the matrix expands horizontally.
Issue 1: Managing Page Width in PDF Export
When exporting the paginated report to PDF, the dynamically generated columns can exceed the page width.
Questions
- What is the recommended approach for handling matrices with dynamically growing columns when exporting to PDF?
- Is there a way to automatically scale the matrix to fit the PDF page width?
- Are there any best practices for:
- Switching between portrait and landscape layouts?
- Splitting columns across multiple pages?
- Using page breaks for column groups?
- Handling a variable number of dynamic columns?
Issue 2: Extra Blank Page Appearing in PDF Export
In addition to the width issue, each report page is followed by an extra blank page when exported to PDF.
Current Settings
- Report has a fixed page size.
- Margins appear to be within normal limits.
- Matrix width changes dynamically based on Product Type values.
Questions
- Can dynamic matrix width cause additional blank pages during PDF export?
- What are the common causes of a blank page being generated after every report page?
- What should I check to identify whether the issue is caused by:
- Report body width
- Matrix width
- Rectangles/containers
- Page size and margins
- Hidden objects extending beyond the printable area
Expected Outcome
I would like the report to:
- Export to PDF without creating extra blank pages.
- Handle a varying number of Product Type columns gracefully.
- Maintain readability even when the matrix expands horizontally.
Any guidance, best practices, or examples would be greatly appreciated.
Thanks!
5 Replies
Hi NB8,
Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to ShivekMaharaj for sharing valuable insights.
Could you please confirm if your query has been resolved by the provided solutions? This would be helpful for other members who may encounter similar issues.
Thank you for being part of the Microsoft Fabric Community.
Hi v-abhinavmu,
Thank you for checking in. At this time, the issue has not been resolved. I reviewed and tested the suggested solutions, but they did not address the problem in my scenario.
I am still looking for a solution and would appreciate any further assistance or recommendations from the community.
Thank you.
Hi NB8,
Thanks for the update. I would recommend checking the following areas based on Microsoft's guidance for paginated reports:• For a dynamic matrix, the Product Type column group can expand horizontally and the PDF renderer can paginate the matrix across multiple pages. Consider using landscape orientation, appropriate margins/column widths, and repeating row headers across horizontal pages for readability.
• For the unexpected blank pages, first verify that the report body width doesn't exceed the available page width:
Report body width <= Page width - (Left margin + Right margin)• Also check for excess whitespace below the report body, unnecessary page breaks on the matrix/groups, and the ConsumeContainerWhitespace property.
• Use Print Preview to determine how the report is being split into physical pages before exporting to PDF.
For more details, please refer to the below Official Microsoft documentation:
Avoid blank pages when printing paginated reports - Power BI | Microsoft LearnRendering Behaviors in a Power BI Paginated Report - Power BI | Microsoft Learn
I hope this helps. Please feel free to reach out if you have any further questions.
Thank you.
Hi NB8,
I would treat these as two related PDF pagination issues.
The important thing with a dynamic matrix is that PDF is a hard-page renderer. As additional Product Type values are returned, the matrix can expand horizontally, but PDF does not automatically shrink all of those dynamic columns to fit the physical page.
Microsoft's paginated report pagination guidance recommends keeping:
Report body width <= Page width - (Left margin + Right margin)For a moderate number of Product Types, landscape orientation, smaller margins and narrower columns can help. If the number of Product Types is potentially large, I would design for horizontal pagination instead of trying to force every column onto one page. You can also repeat the row headers on each page, which makes a matrix much easier to read when it spans horizontally.
For the extra blank page, I would check the report width before anything else. Microsoft's blank-page guidance specifically calls out the report body exceeding the available page width as a common cause.
Check:
Body Width + Left Margin + Right Margin <= Page Widthand also inspect the matrix, rectangles, lines and hidden objects for anything extending slightly beyond the right edge. Because PDF renders physical pages left-to-right before moving down, even a small horizontal overflow can look like a blank page after each populated page.
I would also check that there are no unnecessary page breaks on the tablix/groups and review ConsumeContainerWhitespace, but I would fix any width overflow first.
There isn't a documented automatic "fit dynamic matrix to one PDF page" setting, so if Product Type count can vary significantly, limiting/splitting the column groups or using a wider custom page size is usually more predictable than relying on automatic scaling.
AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.
