paginated-report

Author, validate, publish, and render Power BI paginated reports in RDL format.

6|3|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/InsightfulAnalytics/PBI_Agentic_Dev --skill paginated-report-insightfulanalytics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: paginated-report
Source: https://github.com/InsightfulAnalytics/PBI_Agentic_Dev/tree/main/plugins/paginated-reports/skills/paginated-report
Command: npx skills add https://github.com/InsightfulAnalytics/PBI_Agentic_Dev --skill paginated-report-insightfulanalytics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Hand-authoring Power BI paginated report (.rdl) XML is error-prone: element order breaks files silently, DAX and parameter wiring fail only at render time, and preview never matches PDF output. This Skill provides the RDL format rules, starter templates, validation scripts, and a publish-and-render loop so reports actually work in the Power BI service. ## Core Features & Use Cases - RDL authoring guidance: Detailed references covering the 2016 RDL schema, element ordering rules, tablix structure, parameters, data source connect strings (PBIDATASET, SQL, Enter Data), and renderer quirks. - Validation and publishing scripts: A stdlib-only Python validator for structural checks, plus Bash/PowerShell scripts that publish via the Power BI Imports API and export rendered output (PDF, Excel, etc.) to confirm the report works. - Starter templates: Ready-to-edit .rdl assets for Enter Data, semantic model (DAX/TREATAS), and Azure SQL sources, plus the Fabric Git .platform sidecar. - Use Case: A user asks to build a print-perfect invoice report connected to a Power BI semantic model. The Skill runs a requirements interview, copies the semantic-model starter, wires a verified DAX query, validates the XML, publishes to a capacity-backed workspace, and exports a PDF to confirm the rendered output. ## Quick Start Ask the agent to create a paginated invoice report connected to your Power BI semantic model and render it to PDF for verification.

Frequently Asked Questions about paginated-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Power BI paginated report from an RDL file?▼

Start from a starter .rdl template, edit the XML layout against an embedded Enter Data dataset, then swap in the real data source. Validate with the structural validator script, publish via the Power BI Imports API, and export to PDF to confirm the report renders correctly.

How do I connect a paginated report to a Power BI semantic model?▼

Use the PBIDATASET data provider with a connect string containing the sobe_wowvirtualserver-<dataset GUID> catalog and Integrated Security=ClaimsToken. The dataset query is DAX; column fields use Table[Column] naming and measures use [Measure] naming.

Why does my hand-edited RDL file fail to load in Report Builder?▼

Element order is load-bearing: the report processor rejects out-of-order children with no useful error, and XSD validation will not catch it. Preserve the documented element order and run the validate_rdl.py script after every structural edit.

Why does my paginated report PDF have blank pages?▼

Blank pages appear when body width plus left and right margins exceeds the page width, causing hard renderers to emit overflow pages. For landscape Letter with 0.5in margins, keep body width at or under 10 inches.

What is the difference between Power BI paginated reports and SSRS?▼

Both use the same RDL format and Report Builder, but Power BI paginated reports run in the Power BI service on Premium or Fabric capacity, require embedded data sources, and add the PBIDATASET provider for semantic models. Shared data sources, snapshots, and data-driven subscriptions are SSRS-only.

Can I preview a paginated report instead of exporting to PDF?▼

Preview in Report Builder and the service browser always uses the HTML soft page-break renderer, so page counts, margins, and headers differ from PDF output. Always verify the delivery format by exporting to it with the export-to-file API.