Power BI paginated reports

Power BI's headline experience is interactive reports — dashboards built in Power BI Desktop, browsed in the service. But every Power BI deployment of any size eventually needs the other report type: paginated reports — pixel-perfect, page-oriented documents born from SQL Server Reporting Services (SSRS).

Why the distinction. Interactive Power BI reports excel at exploration: filters, drillthrough, slicers, charts. They don't excel at print: a 47-page month-end pack with vendor statements, regulatory submissions, customer invoices. For these, paginated reports are the right tool.

Paginated reports in short.

• Lineage: SSRS RDL format.
• Designed in Power BI Report Builder (free download).
• Hosted in the Power BI service or Power BI Report Server.
• Output formats: PDF, Excel, Word, CSV, image.
• Page-based — explicit page breaks, headers, footers.
• Data-bound at runtime via parameters.

Use cases for paginated.

• Regulatory submissions — government forms with exact layouts.
• Customer-facing invoices and statements — branded, printable.
• Operational reports — picking lists, packing slips, daily sales by store, formatted for printer.
• Long tabular exports — sub-ledger details, audit packs.
• Email blasts — generate a PDF per customer with personalised content.

Designing a paginated report. Open Report Builder:

1. Data source — connect to a Power BI semantic model, SQL Server, Azure SQL, Dataverse, or OData.
2. Dataset — query the data source.
3. Layout — drag controls onto pages: tables, matrices, charts, text boxes, images.
4. Parameters — define inputs the user provides (date range, customer ID).
5. Formatting — fonts, colours, page size, headers, footers.
6. Preview — runtime test.
7. Publish to Power BI service.

The design experience is more traditional than Power BI Desktop — closer to Crystal Reports or SSRS than to modern interactive design tools.

Data sources. Paginated reports can query:

• Power BI semantic models (modern recommended path).
• Azure Synapse, Azure SQL, on-prem SQL via gateway.
• Dataverse.
• OData feeds.
• Many others through extensions.

A modern pattern is centralising in a Power BI semantic model and having paginated reports query the same model — single source of truth across interactive and paginated.

Hosting.

• Power BI service — the cloud, requires Premium or PPU.
• Power BI Report Server (PBIRS) — on-prem alternative, useful for sovereignty requirements. Slower release cadence; tend to lag service features.

Triggering reports.

• Manual — user opens the report and provides parameters.
• Subscription — email schedule sends PDF to recipients.
• Power Automate — flow generates the report with parameters and routes the output (email, attach to a record, save to SharePoint).
• API — programmatic generation.

The Power Automate integration is the workhorse for operational delivery — "every Monday email each sales rep a paginated PDF of their week ahead."

Comparison to interactive Power BI.

| Aspect | Interactive | Paginated | |---|---|---| | Purpose | Exploration | Print/export | | Layout | Flexible canvas | Pixel-precise | | Output | Browser experience | PDF/Excel/etc | | Author | Power BI Desktop | Report Builder | | Data | Semantic models | Many sources | | Parameters | Slicers (in-report) | Run-time inputs | | Hosting | Service / PBIRS | Service / PBIRS |

Where paginated is still essential.

• Anything that needs to be printed or emailed as a static document with fixed layout.
• Regulatory-format submissions with strict pagination.
• High-volume per-record generation (10,000 customer statements at month end).

Modern alternatives.

• Power BI mobile — interactive but mobile-friendly.
• Export to PDF from interactive — works for simple cases, awkward for complex.
• Generate documents from Power Automate — Word templates, dynamic PDF generation; for documents with limited data and high formatting needs, sometimes simpler than paginated.

Common pitfalls.

• Migrating SSRS reports as-is. They work but look dated; consider redesign in Report Builder.
• Overcomplicated queries inline. Heavy SQL embedded in datasets; performance hit. Push to views or semantic models.
• No subscription discipline. Reports emailed forever to people who left; subscription audit is a recurring hygiene task.
• Wrong tool choice. Building an exploration scenario as paginated, or a printable scenario as interactive — both lead to friction.
• Forgotten data refresh dependencies. Paginated against an out-of-date semantic model emails wrong numbers.

Operational guidance. A mature Power BI deployment uses both: interactive for analytical consumption, paginated for operational document delivery. Treat them as complementary, not competing. The teams that try to force one to do the other's job end up with frustrating experiences and unhappy users.