Forum Discussion
PDF Export Missing HTML Table Content
- 1 month ago
Hi Dynizju,
Unfortunately, I don't believe there is a native way for Power BI report exports to automatically split a scrollable visual across multiple PDF pages. The same has been answered in another post - PDF export do not show full table
What you're seeing is expected behaviour. When exporting a standard Power BI report to PDF, only the visible portion of a scrollable visual is captured. Any rows that require scrolling are not included in the PDF export.
Given your scenario, simply increasing the page height isn't ideal because the number of rows varies based on the selected filters. You would either end up with truncated data or large amounts of unused whitespace.
For requirements where the full table must be exported regardless of the number of rows, the recommended approach is typically a Paginated Report. Paginated Reports are designed for exactly this use case and will automatically flow table data across multiple pages when exported to PDF, ensuring all rows are included without requiring scrollbars.
If moving to Paginated Reports isn't an option, the alternatives are generally limited to:
- Exporting the underlying data to Excel/CSV instead of PDF.
- Redesigning the report to reduce or eliminate scrolling.
- Using a dedicated printable report page specifically for export purposes.
So in short, if the requirement is"export all rows to PDF and automatically span multiple pages", I would strongly recommend a Paginated Report. Standard Power BI report exports don't currently support automatic pagination of scrollable visuals during PDF export.
If my answer helped you solve the problem, please consider accepting it as the solution and help other members to use the same solution in same/similar situations.
Hi Dynizju
If your requirement is Export all table rows to PDF, with automatic page breaks, regardless of row count then the best approach is to use a Paginated Report.
Best approaches
1) Use a native Power BI table or matrix visual
If the goal is exportable tabular data, this is usually the best option.
Why it helps:
- Native tables/matrices are much better supported in export
- They can span multiple pages in PDF more predictably than HTML visuals
- You can use formatting, conditional formatting, row padding, and column sizing to improve appearance
Limitations:
- Still not as flexible as custom HTML
- Very long tables can still be awkward, but export behavior is much better
2) Move the table to a paginated report
If you need a true printable document that automatically flows across pages, this is the best-fit solution.
Use Power BI Paginated Reports (Report Builder / SSRS-style reports):
- Designed for invoices, statements, lists, and long tables
- Supports automatic page breaks
- Repeats headers across pages
- Handles variable-length data much better
- Exports to PDF cleanly
This is the closest match to what you want.
3) Use a drill-through or export-only detail report
If the main report is interactive and the detailed table is large, create:
- a summary Power BI report page for viewing, and
- a detail/paginated report for export
That keeps the interactive report clean while giving users a printable output when needed.
4) Split the content yourself before export
If you must stay with the HTML visual, the workaround is to pre-split the data into chunks and display them as separate sections/visuals.
For example:
- Page 1: rows 1–20
- Page 2: rows 21–40
- etc.
But this is usually awkward in Power BI because:
- the split logic must be driven by the data
- it adds complexity
- it still won’t behave like true pagination unless you manage the layout carefully