How to Send Power BI Subscription Emails with Saved Filters

The branch manager has a straightforward question before the weekly meeting: which jobs are still open at this location? The national overview is useful to head office, but it makes the manager work to find the few rows needed for today’s discussion.

Someone on the reporting team already knows the right selections. They open the report, choose the branch, select Open and check the reporting period. The problem is having to repeat that preparation whenever a file is needed.

PBRS makes those choices part of the recurring reporting job. Configure the report filters or supported slicer selections, preview the result, and save the output format and destination with them. The manager can receive a prepared PDF or another supported file without asking a colleague to reconstruct the view each Monday.

Why the browser and the email can disagree

A filter you change while reading a report affects what you see at that moment. It does not necessarily change the view stored in an existing Power BI subscription. That is why the browser can look right while the next email still shows an older selection.

For a standard native report-page subscription, use Include my changes to capture the customized view where that option is available. Leaving it unchecked uses the author’s published report view. When you change an existing subscription’s view, update and save it deliberately.

That may be enough for one stable audience. When several managers need different branches, or the output also needs formatting, protection and delivery to different destinations, PBRS’s data-driven reporting can keep each recipient’s content and delivery choices together.

Before saving anything, decide what should stay fixed and what should move forward. The branch may remain the same for months, while the reporting period needs to change every week.

For our manager, “open jobs” may mean all outstanding work, including older jobs. Filtering to this week’s creation dates could accidentally hide work that still needs attention. Agree what the period means before automating it, and give the report a caption that makes that meaning clear.

Watch the bookmark as well as the filter

A bookmark can contain filter and slicer selections of its own. Microsoft notes that entering a report through a bookmark can cause the subscription to use that bookmark’s filters rather than later selections made while creating the subscription. If that is your route, save a bookmark with the intended view.

PBRS can also apply report bookmarks. Its guidance recommends choosing either a bookmark or report filters where possible, because the two can overwrite each other’s settings. A preview of the combined result matters more than assuming the last visible selection will win.

Keep the audience in mind

A filtered view is not an access-control rule. The static image in a native subscription email reflects the subscription owner’s permitted data, while opening the interactive report uses the reader’s own permissions. Check that the emailed content is appropriate for every recipient.

Use model security, including row-level security where required, to control authorized access. PBRS filters, slicers and bookmarks then select the intended presentation within the reporting workflow.

Start with one branch and a recipient who can recognize its work. A small, familiar example makes it easier to see whether the saved view matches the business request.

Save or update the native subscription

Open the required report page and apply the branch, status and date selections. Select Subscribe, then create a subscription or use the pencil control to edit the existing one. Where available, select More options → Include my changes.

For an existing subscription, use Preview to inspect the stored view before replacing it. Return to the subscription, choose Update under Include my changes, and save. That update applies to the current page; review other subscribed pages separately.

Send a controlled test and read the resulting email. Native Run now sends the subscription; it does not refresh the semantic model. The right filters can still produce old figures if the source data has not been updated.

Include my changes is not available for dashboards or paginated reports; paginated reports use parameters. Creating subscriptions through an org app also has limitations around capturing personalized report state. If the option or result differs, check the report and entry point against Microsoft’s subscription guidance.

Prepare the filtered file in PBRS

In the Power BI Single Report Schedule, open the report’s filter settings and select Add → Basic. Choose the actual model field for the branch, its data type and the comparison operator, then add the required branch value. Add a separate criterion for the Open status.

Under Filter Level, choose Report when you want a report-level filter. Choose Slicer when the schedule should set a particular slicer, identifying it by its Visual Title or Filter Field. These settings use real model fields and controls, which may have different names from the friendly labels a reader sees.

Preview the result, choose the supported output format, and set the destination and recurrence. If the job must refresh the data before producing the file, configure that step as well. The PBRS single-report schedule guide explains those controls.

Give each manager their own useful output

When the same report serves many branches, PBRS data-driven schedules can use recipient records to supply the branch selection and delivery details. You can extend that preparation to supported PDF protection, Excel formatting or report packages, rather than maintaining a separate manual export routine for each manager.

Test the delivered output with a known open job from the intended branch and a job from another branch that should be absent. Check the date caption too. Then test a second recipient so you know the content and address remain correctly paired.

If an application manages the schedule, keep a readable description beside its technical settings: “Branch BR-101, open jobs, all outstanding work.” That gives another owner a way to understand the intended output before reading field names and values.

The PBRS API lets you include filters in the source-specific schedule definition. The example below represents the branch and status selections for our manager; it does not configure recipients, recurrence or the complete reporting job.

{
  "BasicFilters": [
    {
      "TargetField": "Jobs.BranchCode",
      "FieldDataType": "String",
      "FilterLevel": 0,
      "Operator": "In",
      "BasicValues": [
        "BR-101"
      ],
      "IgnoreBlankDataDrivenInserts": false
    },
    {
      "TargetField": "Jobs.Status",
      "FieldDataType": "String",
      "FilterLevel": 0,
      "Operator": "In",
      "BasicValues": [
        "Open"
      ],
      "IgnoreBlankDataDrivenInserts": false
    }
  ],
  "AdvancedFilters": []
}

Make missing values an intentional decision

PBRS’s Ignore filter when insert values are blank option can omit a filter when a data-driven value is missing. For a branch-specific delivery, that could broaden the report. Validate the branch before execution and configure the workflow’s response to missing data; setting a filter flag alone is not a complete stop-delivery policy.

After a field, bookmark or mapping changes, review the output again. For native subscriptions, remember that renaming a report page requires recreating its subscription, and deleting the page removes its subscriptions.

Next Monday, the manager should be able to open the report and begin discussing the work. The branch is already selected, closed jobs are out of the way, and the reporting period means what the team expects.

A native saved view can handle a straightforward subscription. PBRS adds a maintained reporting job around that view, bringing filters, file preparation, refresh and delivery together as the audience grows.

Explore personalized Power BI distribution and the wider Power BI Report Automation workflow. Use the evaluation guide below to test one branch’s report from saved selection to delivered file.

Download the PBRS Internal Evaluation Guide