How to Pass Parameters to Paginated Report Exports in Power Automate

Your finance colleague has finished the monthly statements and wants each customer to receive a PDF. The report looks correct when opened manually, but one exported file still shows the default customer. Before rebuilding the flow, check what it actually sent to the report.

In Power Automate, use Export To File for Paginated Reports, select the published report and add its parameter name/value entries. Use the report’s internal parameter name and an accepted value. The label in a dropdown is not necessarily the value behind it.

Look behind the friendly label

Open the report’s parameter properties in Power BI Report Builder. The Name identifies the parameter; the Prompt is what a reader sees. Available values may pair a customer’s name with a numeric account key.

For this example, suppose the report defines a numeric parameter called CustomerID, and the selected customer’s key is 1042. The flow needs CustomerID and 1042, not the words “Choose a customer” or the company’s display name. Your report may use different names and types.

Give the reporting period the same attention. A text parameter might accept 2026-10, while another report expects separate start and end dates. Check the actual definition instead of assuming that a month label will be understood.

Establish one correct result first

Start with fixed values for one authorized customer and one known period. Compare the exported statement with a manual run of the same report. Once that works, replace the fixed values with the appropriate dynamic fields and inspect the values in the flow’s test run.

PBRS uses the same basic discipline: valid report parameters first, then automation. Its advantage is keeping parameter selection, file preparation and delivery in a reporting schedule, so month-end does not become a growing collection of separately maintained export steps.

A small flow that exports one statement can be perfectly workable. The complications appear when you add many customers, several formats, different destinations and an expectation that failures will be noticed and handled.

Check the parameter rules

For multi-value inputs, follow the connector’s supported parameter collection. Microsoft’s direct paginated export API represents multiple selections by repeating a parameter name with different values. Do not assume that representation transfers unchanged to PBRS or another API. The Microsoft export guide shows its contract.

Allow for Power Automate’s export limits

Correct inputs cannot fix an unavailable export route. Microsoft documents eligible capacity as the standard requirement for this paginated export action, with a limited PPU option of one export within a five-minute window. A Pro license on shared capacity alone does not meet those documented prerequisites.

There is also a documented Power Automate limitation when the report takes more than two minutes to download. For larger customer runs, your team must manage pacing, retries and failed items as well as the parameter mapping. Microsoft’s Power Automate paginated export guidance explains those restrictions and retry considerations.

Why PBRS can be the better fit

PBRS provides reporting-specific controls for data-driven parameters, custom calendars, output preparation, multiple destinations and exception handling. Instead of building each part of the statement-delivery process into a flow, you configure the reporting job and maintain its rules together.

It supports published reports in Power BI Service, Power BI Report Server and SSRS, including supported Pro and PPU scenarios. It does not export directly from Power BI Desktop. Confirm the chosen source, access and export method during evaluation; PBRS still needs authorized access and valid report inputs.

Return to the finance colleague’s statement. They need the right customer, the right month and a file that is ready to send. Use that complete result as the test—not merely a successful export action.

Test two customers with different results

After confirming customer 1042, try another authorized customer whose statement has visibly different figures. If both PDFs still show the same customer, inspect the mapping for a value that remained fixed. Check the report heading, dates and a known balance in each file.

Keep the recipient paired with the customer key throughout the workflow. Parameters select content; they do not establish permission to receive it. A correct PDF sent to the wrong address is still a failed delivery.

Configure the recurring job in PBRS

Select the published paginated report and enter the parameter names, values and types required by that report. Preview the result before adding the delivery destination. Decide how the period will advance each month so the job does not keep sending a correctly rendered statement for an old period.

For many customers, use a data-driven schedule to supply the appropriate parameter values and recipient information from the configured data source. That lets one maintained process produce individual statements while the customer mapping remains visible and reviewable.

Prepare the document the recipient needs

Choose a PDF for a statement intended to be read or printed, or a supported Excel export when the recipient needs a workbook. With paginated reports, the report design shapes the exported layout, so inspect page breaks, column widths and totals in the finished format.

PBRS can combine related supported outputs into one PDF or workbook, apply supported file protection, and route results to email, SharePoint, SFTP or other configured destinations. A customer who needs a protected statement and a finance team that needs a shared archive can be served within the reporting workflow.

Decide what should happen when a statement has no data and how a failed job should be handled. PBRS provides blank-report handling, notifications, retries and alternative actions where configured. These rules belong in the setup, before the first unattended month-end run.

Finish with a controlled delivery

Send the test output to an approved test destination. Open the final protected or merged file, check its customer and period, and verify that the recipient mapping is correct. Then enable the agreed recurrence or event trigger.

The benefit is a routine your colleague can understand: the customer list supplies the selections, PBRS prepares the statements, and the configured delivery rules get each file to its destination. The team can investigate a particular run instead of manually rebuilding the whole batch.

If a finance application supplies the customer and reporting period, it can update an existing PBRS paginated schedule through the API. Read the saved configuration first, preserve the parameters that should remain and verify the update before execution.

The example assumes a report with exactly two parameters: numeric CustomerID and text ReportingMonth. The values are illustrative, and the code changes saved configuration. Test against a dedicated schedule and controlled destination.

GET {pbrsBaseUrl}/api/SingleSchedule/GetPaginated?Id=101
Authorization: bearer {pbrsAccessToken}

POST {pbrsBaseUrl}/api/SingleSchedule/UpdateParametersPaginated
Authorization: bearer {pbrsAccessToken}
Content-Type: application/json

{
  "uniqueid": 101,
  "Parameters": [
    {
      "ParameterName": "CustomerID",
      "ParameterValue": "1042",
      "ParameterType": 1,
      "IsNull": false
    },
    {
      "ParameterName": "ReportingMonth",
      "ParameterValue": "2026-10",
      "ParameterType": 0,
      "IsNull": false
    }
  ]
}

Keep concurrent customer requests isolated

Updating parameters and executing a job are separate operations. If two requests modify the same schedule at once, one can overwrite the other’s customer selection. Use an appropriate data-driven design, separate schedules or controlled serialization across update, verification and execution. Do not treat the example as an atomic per-customer export.

That detail matters to the reader waiting for a statement: the application must keep the requested customer, generated file and intended recipient connected from beginning to end.

The next month-end should not begin with someone wondering whether the flow remembered the right customer. Start with verified inputs, test the finished statement and keep the delivery mapping with the job.

Keep Power Automate when a straightforward flow meets the requirement and its limits fit the workload. Choose PBRS when the recurring task needs data-driven personalization, document preparation, several destinations and reporting-specific handling of failures or empty results.

Explore PBRS paginated report scheduling and the wider Power BI Report Automation workflow. Use the evaluation guide below to test two real customer scenarios before rolling out the monthly batch.

Download the PBRS Internal Evaluation Guide