Paginated Reports in Power BI: When and How to Use Them

Most Power BI reports are interactive — designed for exploration, with slicers to filter, visuals to cross-highlight, and charts to drill into. These interactive reports excel at helping users discover insights. But they're the wrong tool when the requirement is a formatted invoice, a regulatory filing, a financial statement that must print identically on every printer, or a report that spans hundreds of pages with consistent headers and footers on each one.

Power BI paginated reports are the answer to these requirements. Built on the mature SQL Server Reporting Services (SSRS) report definition (RDL) technology, paginated reports produce pixel-perfect output that renders consistently across screens, PDFs, Excel exports, and print. This guide covers when paginated reports are the right choice, how to build them, and the deployment and subscription patterns that make them operational reporting workhorses.

Key Takeaways

• Paginated reports are designed for printing, exporting, and pixel-perfect formatting — not interactive exploration
• They use Report Builder or Power BI Report Builder (free) as the authoring tool, not Power BI Desktop
• Data sources include Power BI datasets, SQL Server, Oracle, Azure SQL, and any ODBC/OLE DB source
• Tables and matrices in paginated reports can span thousands of rows across hundreds of pages
• Subreports, nested data regions, and complex grouping support highly structured financial formats
• Parameters allow users to specify date ranges, entities, or other filters at render time
• Subscriptions deliver reports automatically via email or SharePoint on a scheduled basis
• Paginated reports require a Power BI Premium, Premium Per User, or Fabric workspace to publish

---

Interactive Reports vs. Paginated Reports

The right tool depends on the use case. Understanding when each report type is appropriate prevents the common mistake of forcing paginated report requirements into interactive dashboards (or vice versa).

The decision rule is straightforward: if the output is defined by structure (a formatted document with specific content in specific places), use paginated reports. If the output is defined by exploration (letting the user discover what's interesting), use interactive reports.

---

Power BI Report Builder

Power BI Report Builder is the free authoring tool for paginated reports, available as a separate download from Microsoft. It uses the same RDL format as SSRS and produces reports that publish to Power BI workspaces.

Key interface areas:

• Design surface: A pixel-precise canvas where report items (textboxes, tables, matrices, charts, images) are placed with exact coordinates
• Report Data pane: Manages data sources, datasets (queries), parameters, and images
• Properties pane: Controls formatting, visibility, expressions, and behavior of each element
• Report toolbar: Preview, zoom, and page navigation

Creating a new report:

1. Open Power BI Report Builder → New Report → Blank Report
2. In Report Data → New → Data Source → select Microsoft Power BI Dataset or a database connection
3. Create a Dataset with the query that retrieves report data
4. Add a table or matrix to the design surface
5. Map dataset fields to table columns
6. Configure formatting, grouping, totals, and headers/footers
7. Preview → Save → Publish to a Premium workspace

---

Data Sources for Paginated Reports

Paginated reports support a wider range of data sources than Power BI Desktop interactive reports:

Power BI datasets: Connecting a paginated report to a Power BI semantic model (via the Power BI Dataset data source type) is the recommended approach for organizational consistency — the paginated report uses the same governed data and measure definitions as interactive reports.

SQL Server and Azure SQL: Direct database connections using SQL queries. This is common for detail-level reports where the semantic model's aggregated data is insufficient — you need individual transaction rows, not measure-level summaries.

Oracle, PostgreSQL, MySQL: Supported via ODBC connections.

OData feeds: REST API data sources that expose OData protocol.

Azure Analysis Services: For organizations using AAS as the analytical layer, paginated reports can connect directly.

Embedded parameters in queries: Unlike Power BI Desktop import mode (where the query runs once at refresh), paginated reports run queries at render time with user-supplied parameters. A query like WHERE OrderDate BETWEEN @StartDate AND @EndDate filters the database at query execution, not at data model load time.

---

Tables and Matrices: The Core Report Structures

Paginated reports are built around two primary data regions: tables (fixed columns, variable rows) and matrices (variable rows and columns — pivot table style).

Table structure for a simple financial detail report:

[Header]
Report: Accounts Payable Aging as of @ReportDate
Entity: @EntityName

[Table]
| Vendor Name | Invoice # | Invoice Date | Due Date | Amount | Days Overdue |
|-------------|-----------|--------------|----------|--------|--------------|
| [row details iterate here] |

[Table footer]
| Total | | | | [Sum(Amount)] | |

The table automatically generates as many rows as the dataset contains. A table with 50,000 rows generates 50,000 detail rows across however many pages are required, with consistent column headers on each page.

Grouping organizes rows hierarchically. A general ledger report might group by Account Category → Account → Cost Center, with subtotals at each group level:

• Account Category: Revenue (subtotal)
  • Account 4001: Product Revenue (subtotal)
    • Cost Center 100: $485,000
    • Cost Center 200: $312,000
  • Account 4002: Service Revenue (subtotal)

This nested grouping with subtotals at each level is straightforward in paginated reports but complex to implement in Power BI interactive visuals.

Matrix (crosstab) creates a dynamic pivot structure where columns are generated from data values, not predefined. A budget vs. actual matrix might have months as columns, generated dynamically so the same report definition works for any date range parameter.

---

Parameters: Making Reports Dynamic

Parameters are the user-input mechanism for paginated reports. At render time, the user specifies parameter values (or they're supplied programmatically) and the report queries and formats accordingly.

Common parameter types:

• DateTime: Start/end dates for the report period
• Text: Entity name, department, cost center
• Integer: Report year, fiscal period
• Boolean: Include inactive records, show zero-value rows
• Multi-value: Allow users to select multiple departments or regions

Parameter cascading means one parameter's available values depend on another's selection. Select a Company → the Department parameter filters to departments in that company → the Cost Center parameter filters to cost centers in that department. This is configured using parameterized dataset queries:

-- Departments dataset query (filtered by selected Company)
SELECT DepartmentID, DepartmentName
FROM Departments
WHERE CompanyID = @CompanyID
ORDER BY DepartmentName

Default values can be expressions that calculate at render time. A date parameter defaulting to =Today() always opens to today's date. A period parameter defaulting to =Month(Today()) opens to the current month.

---

Formatting and Expression Language

Paginated reports use Visual Basic expressions (prefixed with =) for dynamic formatting, visibility, and content. This is different from DAX — it's a different language for a different runtime.

Common expression patterns:

Conditional color based on value:

=IIF(Fields!Variance.Value < 0, "Red", "Black")

Alternating row colors (for readability):

=IIF(RowNumber(Nothing) MOD 2 = 0, "LightGray", "White")

Formatting a number as currency:

=Format(Fields!Amount.Value, "C2")

Formatting as percentage:

=Format(Fields!Variance.Value, "P1")

Page numbering:

=Globals!PageNumber & " of " & Globals!TotalPages

Visibility expressions hide or show rows, columns, and entire sections based on parameter values or data conditions:

=IIF(Parameters!ShowDetail.Value = False, True, False)
-- True = hidden, False = visible

Toggle visibility enables interactive show/hide within the rendered report — clicking a group header expands or collapses the group's detail rows.

---

Page Layout and Print Optimization

The "paginated" in paginated reports means the layout is designed around pages — specific page sizes (A4, Letter, Legal, custom), margins, headers, footers, and page break control.

Page headers and footers appear on every page and typically contain:

• Report title and company name (header)
• Page number, report date, and confidentiality notice (footer)

Page break control determines where data groups start new pages:

• PageBreakAtStart on a group means each group starts on a new page
• PageBreakAtEnd forces a new page after the group
• KeepTogether prevents a group header from orphaning on the last line of a page

Page sizing: Set page size and margins in Report Properties. Common configurations:

• Letter (8.5" × 11"), Landscape for wide tables, 0.5" margins
• A4 for European distributions
• Custom sizes for specific form prints (invoices, checks)

Column spanning allows a cell to merge across multiple columns for headings — useful for creating financial statement layouts where account names span across period columns.

---

Export Formats and Subscriptions

Paginated reports export to multiple formats:

• PDF: Most common — pixel-perfect, printable, signable
• Excel (xlsx): Data-friendly export, preserving table structure for further analysis
• Word (docx): For reports embedded in Word document workflows
• CSV: Data export, loses formatting
• XML: Structured data export
• PowerPoint: For embedding report snapshots in presentations

Subscriptions deliver reports automatically without user action:

Standard subscriptions send reports to a list of email addresses on a schedule (daily, weekly, monthly, event-driven). Each recipient receives the same report.

Data-driven subscriptions use a dataset to determine recipients and parameter values. A weekly sales report sent to regional managers, where each manager receives only their region's data, uses a data-driven subscription with:

• A dataset containing manager email addresses and their region codes
• Parameters mapped from the dataset (Region = [RegionCode] from the dataset row)
• Each manager receives a personalized report for their region automatically

Data-driven subscriptions require Power BI Premium.

---

Frequently Asked Questions

Do paginated reports require Power BI Premium?

Yes. Paginated reports must be published to and rendered in a Power BI Premium workspace (Premium Per Capacity, Premium Per User, or Microsoft Fabric F64+). They cannot be hosted in a Pro-only workspace. Viewing shared paginated reports may require a Premium Per User license depending on workspace configuration. Power BI Report Builder (the authoring tool) is free to download and use for development.

What is the difference between paginated reports and regular Power BI reports?

Regular Power BI reports are interactive — built in Power BI Desktop, designed for exploration with slicers and visual interactions. Paginated reports are document-oriented — built in Power BI Report Builder, designed for printing, exporting, and structured output. Interactive reports work best for dashboards and self-service analytics. Paginated reports work best for financial statements, invoices, regulatory filings, and any report that must print correctly or be exported to exact specifications.

Can paginated reports connect to a Power BI semantic model?

Yes. Using the "Power BI Dataset" data source type, paginated reports connect to published Power BI semantic models and query them using DAX. This allows paginated reports to use the same governed measures, hierarchies, and security (including row-level security) as interactive reports — ensuring consistency between the two report types. This is the recommended approach for organizations with established semantic models.

How do I convert an SSRS report to Power BI paginated reports?

Power BI paginated reports use the same RDL format as SSRS, so most SSRS reports can be published to Power BI by changing the data source connections. Data source types supported in SSRS but not in Power BI (like Analysis Services in certain configurations, or some older ODBC drivers) may require reconfiguration. The report layout, expressions, grouping, and most formatting work identically. Upload the .rdl file to a Premium workspace to test compatibility.

Can paginated reports be embedded in custom applications?

Yes. Power BI Embedded supports paginated reports using the same embed token and iframe embedding approach as interactive reports. This allows custom applications (customer portals, ERP add-ons, SharePoint) to render paginated reports for their users. The embedded reports can accept parameter values from the application, enabling personalized report experiences without user interaction with parameter prompts.

How do I handle large datasets in paginated reports?

Paginated reports handle large datasets well because they render server-side and page the output — unlike interactive Power BI reports that load all data to the browser. A paginated report with 500,000 rows generates pages as the user navigates, not all at once. For very large datasets, pagination with user-specified parameters (date ranges, entity filters) is strongly recommended to keep render times under 30 seconds. Direct SQL connections with efficient parameterized queries are more appropriate than in-memory import datasets for large-row paginated reports.

---

Next Steps

Paginated reports fill a critical gap in Power BI's capability — providing the pixel-perfect, print-ready, subscription-delivered reporting that operational and financial teams depend on. The technology is mature, the tooling is free, and the integration with Power BI's semantic layer ensures consistency with your interactive analytics.

ECOSIRE's Power BI dashboard development services include paginated report design and implementation, data-driven subscription configuration, and integration with existing Power BI semantic models. Contact us to discuss your formatted reporting requirements.