Power BI Paginated Reports vs Interactive Reports

Power BI has two kinds of report, and they are built for different jobs. Interactive reports, the .pbix reports built in Power BI Desktop, are for exploring and monitoring: click a bar and everything filters. Paginated reports, built in Power BI Report Builder, are for documents: invoices, statements, regulatory reports and long lists that must print exactly and completely. Microsoft describes paginated reports as designed for printing or sharing, with exact control of the page layout (Microsoft Learn: paginated reports).

The difference that matters most: every row

Put a long table in an interactive report and the page shows some rows with a scroll bar. Print it, or export the page to PDF, and only the visible rows appear. Put the same table in a paginated report and printing or exporting produces as many pages as needed for every row. If a report's purpose is a complete document, that alone decides the choice.

Side by side

When to choose a paginated report

• The output is a document: an invoice, a customer statement, a delivery note or a certificate, often one per customer or order.
• Every row must appear: a full transaction list for an auditor, an inventory count sheet.
• The layout is prescribed: a regulator's form, a board pack with fixed page positions.
• People receive it rather than explore it: a PDF by email every Monday morning.

When to choose an interactive report

• Questions change, and readers need to slice, drill and compare.
• The audience monitors trends and KPIs rather than reading lists; Microsoft's design tips centre on showing the most important information at a glance (Microsoft Learn: dashboard design tips).
• Speed of change matters: pages are quicker to redesign in Desktop than pixel-exact layouts.

Many organisations use both on the same data: an interactive report for managers, and a paginated report, built on the same Power BI semantic model, for the documents that go to customers or auditors. Power BI dashboard design covers the interactive side.

A worked decision

A finance team asks for "the receivables report". Asking what happens to it settles the format. The credit controller wants to see which customers are overdue, sort by days outstanding and drill into one account: that is an interactive report. At month end, every customer must receive a statement listing each open invoice, on letterhead, as a PDF: that is a paginated report, with a customer parameter and a page break per customer. Both can read the same semantic model, so the overdue totals agree.

Building a first paginated report

1. Download and install Power BI Report Builder, a free standalone authoring tool.
2. Connect to a data source; a published Power BI semantic model is often the simplest, since its measures and relationships are already defined.
3. Use a wizard, such as the Table or Matrix wizard, to create a dataset and a first layout; free-form list regions suit documents such as invoices.
4. Add parameters, such as a customer or a date range, so each run returns the right slice of data.
5. Set page size, margins, headers and footers, and preview how it prints.
6. Publish to a workspace in the Power BI service; if the data is on-premises, point the connection at a gateway, as covered in the gateway guide.

Paginated reports created for SQL Server Reporting Services 2016 or later, or for Power BI Report Server, are compatible with the Power BI service, which eases migrations, though not every feature carries over.

Licensing and distribution

Licence requirements for paginated reports are the same as for Power BI reports. With a free licence you can publish to My workspace; publishing to other workspaces needs Pro or Premium Per User and at least the Contributor role, plus Build permission on the semantic model used. Paginated reports can be shared, promoted through deployment pipelines, and sent as scheduled email subscriptions; publishing, sharing and workspaces covers the rest of the service.

Limitations to know

• They cannot be pinned to Power BI dashboards.
• Document maps do not render in the Power BI service.
• Shared data sources and shared datasets in the SQL Server Reporting Services style are not supported; data sources are embedded in each report, or a Power BI semantic model is used.
• Data-driven subscriptions from SQL Server Reporting Services are not supported; dynamic per-recipient subscriptions serve a similar purpose, sending each recipient a version filtered for them.

Publishing reports, sharing and workspace management in the Power BI service are part of the Power BI course.

Sources

• What are paginated reports in Power BI? (Microsoft Learn) — Microsoft Learn
• Tips for designing a great Power BI dashboard (Microsoft Learn) — Microsoft Learn