Forum Discussion
Paginated Report Matrix with Dynamic Columns Causing PDF Export Issues
Hi NB8,
Thank you for the clarification and for confirming that you have already tested the previously suggested settings.Regarding your question about repeating row headers across horizontal pages, Microsoft documents Repeat header rows on each page under Tablix Properties > Row Headers for a tablix data region.
For more specific control, Microsoft also documents using Advanced Mode in the Grouping pane to select the appropriate static row member and set:
• RepeatOnNewPage = True
• KeepWithGroup = AfterThe selected static tablix member then repeats on each page that the tablix spans. Microsoft also notes that RepeatOnNewPage isn't supported for column group members.
For the PDF behavior, Microsoft explains that PDF uses a hard-page-break renderer. The physical page size determines where horizontal and vertical page breaks occur, and the page size doesn't automatically grow or shrink to accommodate the report body. If the report body extends beyond the physical page width, a horizontal page break is inserted.
For the blank-page issue, since you have already checked the previously mentioned settings, Microsoft recommends ensuring that the report body width doesn't exceed the available page width:
Report body width <= Report page width - (Left margin + Right margin)
Microsoft also recommends removing unnecessary trailing space from the report body and checking that unnecessary page breaks aren't enabled.
Based on these documented behaviors, you can verify the appropriate static row members in the matrix and confirm that the repeating-header properties are configured as described above.
For more details, please refer to the below official Microsoft documentation:
Show Row and Column Headers on Multiple Pages in a Power BI Paginated Report - Power BI | Microsoft LearnPagination in Power BI Paginated Reports - Power BI | Microsoft Learn
Avoid blank pages when printing paginated reports - Power BI | Microsoft Learn
I hope this clarifies the expected behavior and the relevant settings to check.
Thank you.
Community ChampionHi 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.