paginated-report-ops

Export, rebind, and import Fabric paginated report .rdl files.

14|3|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/patrikborosch/AnalyticsPlatformAgents --skill paginated-report-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paginated-report-ops
Source: https://github.com/patrikborosch/AnalyticsPlatformAgents/tree/main/creator/skills/paginated-report-ops
Command: npx skills add https://github.com/patrikborosch/AnalyticsPlatformAgents --skill paginated-report-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires azure-cli, and includes scripts (resource) components.

What problem does it solve?

Fabric paginated reports lack native support for server-side data source rebinding and streamlined folder management via REST APIs, forcing users to manually edit .rdl XML files and make individual API calls for common tasks like migrating reports from on-prem Power BI Report Server or reorganizing workspace content.

Core Features & Use Cases

  • Export & Import Operations: Download .rdl files from Fabric workspaces and upload modified versions back via the Power BI Import API, with proper multipart encoding to avoid file corruption.
  • Data Source Rebinding: Automatically replace all data source references in .rdl XML to point to a target Fabric semantic model, eliminating manual XML edits for PBIRS-to-Fabric migrations.
  • Folder Management: Move paginated reports between workspace folders using the Fabric REST API, with fallback logic for unreliable direct import placement.
  • Use Case: A team migrating 30 on-prem paginated reports to Fabric can use this skill to batch-repoint all data sources to new cloud semantic models and import them into organized workspace folders in minutes, instead of hours of manual work.

Quick Start

Use the paginated-report-ops skill to export your Fabric paginated report, rebind its data source to the 'Q3_Sales_Model' semantic model, and import it into the 'Marketing Reports' workspace folder.

Frequently Asked Questions about paginated-report-ops

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

FAQPage Schema
How do I rebind paginated report data sources to a Fabric semantic model?

Fabric lacks native server-side data source rebinding for paginated reports, so this skill automates XML editing and semantic model ID resolution to repoint .rdl files without manual intervention.

Can I migrate on-prem Power BI Report Server paginated reports to Fabric?

Migrating on-prem PBIRS paginated reports to Fabric requires downloading .rdl files, automatically modifying their XML data source references to target Fabric semantic models, and uploading them via the Power BI Import API.

Does the Fabric REST API support moving paginated reports between workspace folders?

The Fabric REST API supports moving paginated reports between workspace folders, though direct import placement is unreliable; this skill uses fallback logic to ensure reports reach the correct folders.

Why do my .rdl files get corrupted when uploading to Fabric workspaces?

File corruption during .rdl uploads to Fabric is caused by improper encoding; this skill applies correct multipart file upload encoding via the Power BI Import API to ensure files transfer intact.

Do I need azure-cli to manage Fabric paginated report operations?

Azure-cli is a required dependency for managing Fabric paginated report operations because it handles the Power BI and Fabric REST API authentication needed for export, rebinding, and import workflows.

What is the best way to batch reorganize paginated reports in a Fabric workspace?

The best way to batch reorganize paginated reports in a Fabric workspace is to automate individual Fabric REST API calls for moving .rdl files between folders, overcoming the platform's lack of streamlined native folder management.