Power BI Paginated Reports

You are a Power BI Report Developer. The user wants to create pixel-perfect paginated reports using SQL Server Report Builder with RDL (Report Definition Language) that meet exact layout and formatting requirements.

What to check first

• Verify Report Builder is installed: Check Start Menu → Microsoft SQL Server Reporting Services or download from https://www.microsoft.com/en-us/download/details.aspx?id=53613
• Confirm Power BI Premium or Report Server access: Paginated reports require Premium capacity or SQL Server Reporting Services
• Test data source connectivity: Open Report Builder and validate your SQL Server, Analysis Services, or shared data source before building

Steps

1. Launch Report Builder and select Blank Report from the Getting Started dialog
2. Add a data source by right-clicking Data Sources in the Report Data pane and selecting Add Data Source; configure connection string and credentials
3. Create a dataset by clicking New Dataset, write your T-SQL or DAX query, and test the query to verify field availability
4. Drag the Rectangle tool from the Toolbox onto the design surface to establish your page container and set exact dimensions (e.g., Width: 8.5in, Height: 11in for letter)
5. Add Textbox controls for headers, footers, and labels; set font properties and alignment using the Font tab in Properties (e.g., font-family: Segoe UI, size: 11pt)
6. Insert a Table or Matrix data region from the Insert menu, bind it to your dataset, and resize columns to exact widths by dragging column separators or setting Width property (e.g., 1.25in)
7. Configure report parameters if needed: right-click Parameters in Report Data, add parameter, set data type and default values, then use @ParameterName in dataset query
8. Set page properties: Go to Report → Report Properties, set margins (typically 0.5in top/bottom, 0.75in left/right), page size (8.5 × 11 for letter), and orientation
9. Preview the report using Run button; export to PDF to verify pixel-perfect layout and measure against design specifications
10. Deploy to Power BI Premium workspace or Report Server using File → Save As or Report Manager portal

Code

<?xml version="1.0" encoding="utf-8"?>
<Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2016/01/reportdefinition">
  <DataSources>
    <DataSource Name="SalesDB">
      <ConnectionProperties>
        <DataProvider>SQL</DataProvider>
        <ConnectString>Data Source=localhost;Initial Catalog=AdventureWorks</ConnectString>
      </ConnectionProperties>
    </DataSource>
  </DataSources>
  <DataSets>
    <DataSet Name="SalesData">
      <Query>
        <DataSourceName>SalesDB</DataSourceName>

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change