Run Standard Package Schedules
Run multiple Power BI, Power BI Paginated, Power BI Report Server or SSRS reports from one schedule. Configure each report’s filters, parameters, format, filename and processing order independently.

PBRS automates the complete reporting process—from scheduling and data-driven personalization to exporting and secure delivery. Generate the right report for every recipient across Power BI Service, Power BI Report Server, Power BI Paginated Reports and Microsoft SSRS—without repetitive manual exports or complex automation flows.
Native Power BI subscriptions and Power Automate can handle straightforward internal report delivery. Choose PBRS when reporting requires personalized outputs, additional export formats, advanced schedules, external recipients, stronger output security or destinations beyond standard email delivery.
Native Power BI Tools
Package Schedules
PBRS package schedules run multiple Power BI, Power BI Paginated and SSRS reports as one coordinated job. Apply report-specific filters and output settings, collate or merge the completed files, and deliver each recipient one complete package—in a single email, password-protected ZIP, bookmarked PDF, consolidated Excel workbook or supported destination.
Run multiple Power BI, Power BI Paginated, Power BI Report Server or SSRS reports from one schedule. Configure each report’s filters, parameters, format, filename and processing order independently.
Use database or JSON data to determine the reports, filters, parameters, recipients, formats, filenames, messages and supported delivery details required for each customer, account, department or location.
Coordinate multiple report schedules when a supported database, file, email or operational event occurs. Control the timing and execution order of the reports and tasks within the package.
Send all completed files as attachments in one email, place them in one encrypted or password-protected ZIP, merge them into a bookmarked PDF, or consolidate applicable Excel outputs into one workbook.
Group completed reports by recipient so each customer or business unit receives one package containing only the reports and data intended for them, with the appropriate security and delivery instructions.
Detect and suppress blank reports, retry failed work, notify an operator or run alternative actions. Add pre-processing and post-processing tasks to support the complete reporting workflow.
PBRS replaces the repetitive process of exporting, renaming, collating, protecting and distributing individual reports with one centrally managed package workflow.
PBRS can use data to determine which reports each recipient receives, how every report is filtered and formatted, and where the completed package is delivered. One data-driven schedule can automatically create, collate and distribute a different report package for every customer, account, department or location.
Use database or JSON data to determine which reports belong in each customer, account, department or location package.
Apply the appropriate filters, parameters, formats, filenames, passwords and other supported settings to every report in the package.
Collate reports for the same recipient and deliver them together, or merge applicable outputs into a bookmarked PDF or consolidated Excel workbook.
Send each completed package in one email or ZIP, or route it to the appropriate folder, FTP location, cloud service or other supported destination.
One PBRS data-driven package can replace dozens—or hundreds—of separately maintained report schedules, subscriptions and delivery workflows.
PBRS can run individual reports or complete multi-report packages on recurring schedules, custom business calendars or qualifying operational events. Reports are generated, assembled and delivered when your business process requires them—not merely at a preset time.
Run reports hourly, daily, weekly or monthly, or use custom calendars, working-day rules, fiscal periods, holidays and month-end schedules.
Start a report or package workflow when qualifying database records are created, modified or deleted.
Run reporting workflows when a file appears or changes, a qualifying email arrives or another supported operational event occurs.
Start and coordinate multiple report schedules and related tasks when a qualifying event occurs, with control over their timing and execution order.
Refresh the required Power BI datasets, wait for the refresh to complete and then continue automatically into report generation, package assembly and delivery.
PBRS makes complete report-package creation part of the business process—not merely another recurring calendar task.
Automated Report Distribution
PBRS automatically distributes individual reports, visual-data exports and assembled report packages in PDF, Excel, CSV and other supported formats. Deliver each completed output through the destination already used by the recipient or business process.
Send individual reports or complete packages to the appropriate recipients, distribution lists or Teams channels. Multiple files can be delivered together in one email or packaged in a ZIP file.
Place current reports, workbooks and completed reporting packages in the Microsoft locations used by your teams and business processes.
Deliver exported reports and completed packages directly to configured cloud-storage locations without manually uploading each file.
Route reports and packages to secure transfer services, internal folders, customer locations and downstream operational systems.
Support reporting workflows that extend beyond email, including collaboration platforms, specialist destinations and physical printing.
Deliver complete reporting packages to customers, partners, suppliers and other external recipients without requiring them to sign in to Power BI.
The result: every recipient receives the complete reporting deliverable in the required format and destination—without manual exporting, collating, uploading or distribution.
Refresh the required Power BI datasets before report generation so every distributed report contains the latest available data.
Common PBRS Use Cases
PBRS is designed for recurring reporting operations where reports must be personalized, packaged, protected, triggered by business events or delivered beyond Power BI.
Generate separately filtered reports for customers, partners, franchisees or account holders, then deliver each version without requiring recipients to sign in to Power BI.
Assemble financial statements, management reports, board books and supporting data into controlled PDF or Excel packages on recurring business calendars.
Run reporting workflows when database, file, email or other supported events occur, so teams receive information when an operational condition requires action.
Create high volumes of recipient-specific outputs using data-driven filters, parameters, formats, filenames, security settings and delivery destinations.
PBRS turns complex, recurring reporting requirements into centrally managed workflows that run consistently without repetitive manual exports.
ChristianSteven Software has helped organizations around the world automate business-critical reporting and dependable report delivery for more than two decades.
Learn how PBRS handles deployment, licensing, scheduling, personalization, Power BI exports and automated report delivery.
Yes. PBRS is installed on a Windows server within your environment. Its application database can be hosted locally or in an enterprise SQL Server instance that you manage.
PBRS runs within your environment and uses the Power BI connections and accounts you configure. ChristianSteven does not host the PBRS application database or store your exported report data.
Microsoft’s Export To File API for ordinary Power BI reports requires Premium, Embedded or Fabric capacity and does not support PPU. PBRS, however, supports applicable Power BI Pro and PPU scenarios using alternative rendering methods. The licensing required still depends on the report source, authentication method and deployment configuration.
Yes. PBRS can export reports to files and deliver them to customers, partners and other recipients. Recipients of these exported files do not need to sign in to Power BI, although interactive access to the original Power BI report remains subject to Microsoft licensing.
Yes. PBRS supports hourly, daily, weekly, monthly, quarterly and annual schedules, along with working-day, holiday, fiscal and custom patterns such as 4-4-5 calendars.
Yes. PBRS can start reporting workflows when database records are created, changed or removed; when files appear or change; when qualifying emails arrive; and in response to other supported system events.
Yes. PBRS can initiate and complete a Power BI dataset refresh before generating the report, helping ensure the exported output contains current data.
PBRS can detect blank reports and suppress them, send them or start another workflow. Exception handling can also retry failed report executions immediately or at a configured later interval.
Yes. One data-driven schedule can repeatedly run the same report with different filters, slicer values, recipients, formats, filenames, messages and destinations.
Yes. Database tables and queries can dynamically determine recipients, filters, output formats, filenames, message content, destinations and other schedule settings at runtime.
Yes. PBRS can combine multiple Power BI, paginated or SSRS report outputs into one ordered PDF. It can also place data from multiple selected Power BI visuals into one worksheet, organize individual visuals on separate worksheet tabs, or merge Excel outputs from multiple reports into one workbook with each report on its own worksheet. With PDF Data Only output, data from multiple selected Power BI visuals can be placed on separate pages of one PDF.
Yes. PBRS can apply separate owner and user passwords—set statically or determined from data—and protect the document with 128-bit encryption. Permissions can control printing, full-resolution printing, copying, editing, filling fields, document assembly, adding notes and copying content for accessibility. PBRS also supports text or graphic watermarks, including company logos, plus expiry dates and custom expiry messages.
Optional PDF DRM can additionally restrict access by approved email address, limit the number of devices that can open the document and limit permitted print attempts. These DRM controls require a separate All-About-PDF Developer License.
PBRS supports PDF, Excel, CSV, Word, PowerPoint, HTML and image outputs, among others. Reports can be delivered through email, Teams, SharePoint, OneDrive, Google Drive, Dropbox, FTP/SFTP, network folders, Slack, printers and other supported destinations.
Yes. PBRS can select named Power BI visuals and schedule their summarized or underlying data for export to Excel or CSV, with up to 30,000 rows per visual-data export.
For larger datasets, PBRS can schedule a Power BI Paginated Report or SSRS report for export to Excel, with up to 1,048,576 rows per worksheet. This makes paginated and SSRS reports the appropriate option when the required Excel output exceeds the Power BI visual-data export limit.
Yes. Microsoft’s Export To File API limits an ordinary-report export job to 50 report pages or individual visual exports. PBRS can use its alternative rendering method to export ordinary reports exceeding that limit. Microsoft’s 50-export ceiling does not apply to paginated reports.
PBRS manages scheduling, rendering, status checking, retry handling, file creation and delivery within one purpose-built workflow. When PBRS uses its alternative rendering method, it is not subject to Power Automate connector throttling or its two-minute synchronous paginated-download limit. Actual throughput can still depend on Power BI capacity, server resources, network conditions, report complexity and data-source performance.
Yes. PBRS can create data-only or formatted Excel workbooks, control column headings, data types, Excel formats and selected row or column totals, and insert exported data into an existing template at a designated cell or the next available position. Multiple visual-data exports can be placed in one worksheet or organized on separate tabs, while report outputs can be merged into one workbook with each report on its own worksheet. Individual, personalized and combined workbooks can be protected with static or data-driven passwords before delivery.
See how organizations use PBRS to automate business-critical reporting at scale.
Start with a free 30-day trial, or book a demo to see how PBRS can handle your scheduling, personalization, exports, security and report-delivery requirements.