Dynamic Subscriptions and Parameters for Power BI Paginated Reports

Imagine you coordinate the monthly training review. The Operations manager wants to see which members of her team still need to complete a course. The Customer Support manager needs the same information for his team, so he can arrange cover while people attend.

You already have a paginated report that answers both questions. You select Operations, choose the month and export a PDF. Then you repeat the process for Customer Support and send the two files. Before long, other managers ask for their own copies.

The report does not need to be redesigned for every manager. It needs the right selections each time it runs. Those selections are its parameters: in our example, the department and the reporting month.

PBRS can read those choices from a maintained delivery list alongside each manager’s email address. The job uses the corresponding values to prepare and send each report, so you can spend less time recreating the same selections before every review.

Power BI also offers native dynamic subscriptions for eligible paginated reports. Whichever route you choose, the useful result is the same: the Operations manager can find her team’s outstanding training without sorting through another department’s detail.

Begin by opening the published report yourself. Choose Operations and the completed reporting month, then look at the detail. Does it contain Operations employees only, or has the selection merely changed the heading? Fix that in the report before automating delivery.

The name a manager recognises may differ from the value the report expects. In our example, Operations is labelled “Operations” but its underlying department value is 101. Customer Support uses 202. The delivery setup must pass those values to the report’s Integer DepartmentId parameter.

Next, decide how the month should work. Both managers need the same completed period. Use a fixed month for the first test so you can compare the outputs, then decide how the recurring job will supply the next period. Running every month does not, by itself, change a fixed September selection.

A native dynamic subscription reads recipient and parameter values from a Power BI semantic model. It can be enough when its capacity requirements and email delivery fit your situation. PBRS uses a data driver to supply the delivery records and lets you maintain the parameters with the output formats and destinations.

Start with Operations and Customer Support, using controlled test mailboxes instead of the managers’ addresses. Prepare two approved delivery records: one for department 101 and one for department 202, both for the same reporting month.

In PBRS, create a Data-Driven schedule for Power BI Service Paginated Reports and select the training report. The data driver is the source of those delivery records. Check its results before using them to address an email or select report content.

In the Parameters wizard, add the report’s actual department parameter, choose its type and insert the matching driver field as its value. Repeat for the month. If the report calls that parameter ReportMonth, use that exact name and the type the report defines; your own report may use a different name or a date rather than a text month code.

Preview each department, choose PDF for the output and map the Email destination to the recipient on the same record. Keep the pairings easy to review: Operations’ address goes with 101, and Customer Support’s goes with 202.

Read the copies the managers will receive

Run the test and open both attachments. Check the department, reporting month and a few familiar employees. An Operations employee should appear in the Operations copy and be absent from the Customer Support copy. Check the outstanding-course totals against the report you rendered manually.

Ask the managers to review an approved test copy as well. Can they find the people who need time to complete training? Once the result is right, set the approved recipients, choose the recurring timing and put the month-update rule in place.

If your application maintains the reporting settings, keep the same department choices clear in its code. Operations means 101 and Customer Support means 202 in this example. A friendly label is useful in the interface; the report still needs its underlying value.

The PBRS parameter example below shows how to represent Operations and a fixed test month for a Power BI paginated report. It is a configuration fragment, not a complete request or a replacement for the data driver that supplies every recipient’s values.

{
  "Parameters": [
    {
      "ParameterName": "DepartmentId",
      "ParameterValue": "101",
      "ParameterType": 1,
      "IsNull": false
    },
    {
      "ParameterName": "ReportMonth",
      "ParameterValue": "2026-09",
      "ParameterType": 0,
      "IsNull": false
    }
  ]
}

At the next review, the Operations manager opens her team’s PDF and starts arranging time for the remaining courses. Customer Support’s manager can do the same for his team. You have a repeatable delivery to maintain, rather than a queue of reports to select and email by hand.

Begin with those two checked copies. Use native dynamic subscriptions where they meet your needs. When you want parameters, formats and destinations managed together, explore PBRS paginated report scheduling and the wider Power BI Report Automation workflow.

Use the evaluation guide to plan a trial around a report your managers already rely on.

Download the PBRS Internal Evaluation Guide