Paginated Report Matrix with Dynamic Columns Causing PDF Export Issues

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 Width

and 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.