You can automate the export of filtered Power BI reports to PDF and Power Point using the Power BI Export to File REST API, Power Automate flows or third-party platforms like BI Helper. The native API and Power Automate options require dedicated Power BI Premium capacity, whereas third-party tools can bypass this requirement and distribute reports using a standard Power BI Pro license.
This article covers the export of standard Power BI reports from Power BI Service. It does not cover Power BI Paginated Reports.
The key requirement in 'report bursting' is to run a single Power BI report, filter it for different recipients (e.g., by region, manager or department) and automatically distribute those personalized versions as PDF or Power Point reports.
You can pass filter parameters to the Power BI Export to File API in your JSON request body. You must pass an array of `reportLevelFilters` specifying the exact target table name and column name in Power BI, along with the string values you want applied during the 'bursting' process. The Export to File API has some serious limitations:
- Requirement of a Premium or Fabric dedicated capacity starting at $4,995/month.
- Inability to automatically capture active slicer selections or export uncertified custom visuals.
- Maximum limit of 50 pages per export.
- Inability to loop through a list of external users to send individualized filter views without complex developer orchestration.
See this article for a detailed explanation on the Export to File API and its usage considerations.
To preserve the current filter state when automating Power BI exports, developers must use the Power BI JavaScript API to capture the active slicers and bookmarks and dynamically inject those parameters into the Export to File POST request. This task cannot be performed by business users; it needs a developer.
To automate report bursting, a developer needs to write a custom code wrapper to automate filter selection and to schedule the report for distribution. Alternatively, you can use Power Automate to create a cloud flow, select the Power BI report and loop the PDF/ PPTX export and delivery process for each filter value.
See this article for a detailed explanation on how to use Power Automate with the Export to File API to automate report bursting.
Whether you write custom code or use Power Automate, Power BI Premium capacity starting at $4,995/month is a prerequisite for report bursting from the Export to File API. It is not supported by Power BI Pro or PPU licenses.
BI Helper is a third-party SaaS platform that automates the export of filtered, pixel-perfect PDF and Power Point files from Power BI. BI Helper connects to Power BI via OAuth2, opens your report in embedded read mode, and applies the defined filters and slicers to generate PDF and Power Point files. It then sends the files via AWS Simple Email Service. Report recipients do not need a Power BI license to receive the attachments, completely bypassing Microsoft's licensing barriers.
Besides addressing all the limitations of the Export to File API noted above, BI Helper has the following key features:
- Cost-effective: Requires just one Power BI pro license ($14/mo) for the sender. BI Helper Standard license starts at $50/mo.
- Easy to use: Browser-based, simple UI and workflow
- Supports external (customers, vendors) and internal (employees) users.
- Secure: SOC 2 Type 2 compliant, hosted in the AWS US East 1 region.
- Scalable: Built on serverless architecture; handles report volumes from a dozen PDFs per month to thousands of reports in a day.
No. BI Helper operates ndependently of dedicated capacities and requires only a single Power BI Pro or PPU license to automate PDFs across your entire organization.
Yes. To do this programmatically, you must pass multiple filter contexts into your API payload. If using BI Helper, you separate multiple slicers in the input table using the pipe operator (`|`).
Power BI exports to PDF do not respect slicer and filter selections by default because the native export functionality renders the default report view published to the workspace. Unless filter parameters are explicitly passed in the API payload or bookmark states, the background rendering process discards the current filter context.
