How to Export Multiple Power BI Report Pages to PDF
Your manager needs three pages for the monthly review. You are still exporting the report, removing the extras and checking the PDF before every meeting.
PBRS can save the page selection and deliver one PDF on schedule, so preparing the same management pack no longer depends on you doing it by hand.
- The monthly review Give your manager a pack that follows the meeting
- Your options Decide whether this is a one-off export or a monthly job
- Set it up Prepare the three-page pack in PBRS
- For developers Have your application request the same management pack
- Your next step Start the next review with everyone on the right page
Give your manager a pack that follows the meeting
Imagine your manager opening the PDF just before the monthly review. She wants to begin with the overall result, move on to sales and then discuss what operations needs to do next. Instead, she has to find those pages among the diagnostic views your reporting team uses to check the data.
You know which three pages she needs: Summary, Sales and Operations. You prepared the same selection last month, and the month before. The report itself is useful; getting the right parts into her inbox has become another recurring task.
PBRS lets you keep that selection in a reporting job, together with the PDF format and delivery destination. Once you have checked the pack, you can reuse the job for the next review instead of assembling the document again.
Start by looking at the three pages together. Does Summary explain the overall position? Does Sales give enough context for the result? Does Operations help the team decide what to do next? Those questions give the export a purpose beyond simply putting several pages in one file.
Keep the reporting month consistent across the pack, too. Selecting the Sales page decides which page is included; choosing September decides which figures it shows. Your manager needs both choices to be right.
Try it without the interactive report
Read the PDF as your manager will. A chart that makes sense after hovering over a bar may need a clearer label when it becomes a static page.
Decide whether this is a one-off export or a monthly job
If this is a one-off request for the whole report, Power BI’s built-in PDF export may be all you need. In the service, choose Export > PDF and leave Only export current page unchecked. Review the options for hidden pages, then open the result to see what was included.
Our manager’s request is different: the same selected pages are needed every month, and the internal diagnostic view should stay out. Saving that selection in PBRS gives the recurring task a home. The reporting team can maintain the pack once and set when and where it is delivered.
Before configuring it, check whether the three sections really belong to one Power BI report. Pages To Render selects pages within a report. If Summary, Sales and Operations are separate reports, you need a packaging workflow as well; selecting page numbers alone will not combine them.
Native export choices and PDF limitations
In Power BI’s export dialog, Current values uses the current report state, including supported filter and slicer changes. Default values uses the author’s original state. For the monthly review, check that your choice produces the intended period.
A report page becomes a PDF page; a scrolling table does not automatically expand into a complete transaction listing. When every detail row must be included, consider a paginated report or a suitable data export.
Some visuals and layouts have export restrictions. Review Microsoft’s PDF export guide and check the actual charts in the file before distributing it.
An application can also use Microsoft’s ExportTo API. That is a separate implementation with its own requirements and responsibility for monitoring, retrieving and delivering the export.
Keep internal pages out deliberately
Agree which pages belong in the management pack. Do not assume a page is excluded just because the reporting team normally keeps it hidden.
Prepare the three-page pack in PBRS
Begin with a test copy addressed to yourself. You want to see exactly what your manager will receive, including the filename and the attachment, before it becomes part of the monthly routine.
In PBRS, create or open a Single Report Schedule for the management report. In Settings, use Pages To Render to select Summary, Sales and Operations. If those are currently pages one, two and three, the selection is 1,2,3.
The Single Report Schedule guide also explains ranges and named selections. Use Preview to check that the selection produces the intended pages in a useful order.
Set the reporting-month filter, then choose the delivery destination and Acrobat Format (*.pdf). Give the file a recognisable name that includes the review and period, so colleagues can find the right copy later.
Read the attachment before setting the recurrence
Run the job and open the delivered PDF. Confirm that Summary, Sales and Operations are present and that the diagnostic page is absent. Then read the dates and a few familiar figures across all three pages. A three-page file is only useful if those are the right three pages for the right month.
Ask your manager to try the test copy. Can she follow the discussion from the overall result to the sales detail and the operational response? If chart labels are too small or a page needs explanation, adjust the report before automating the handoff.
Once the pack is ready, switch to the approved destination and schedule it after the monthly figures are available. Check how the month selection advances, so the next run does not quietly repeat September.
If you maintain rendering settings as JSON
The PBRS wizard supports a JSON configuration as an alternative to the Settings controls. The two can overwrite one another, so choose which configuration your team will maintain and follow the guide consistently. Preview again after a change.
Pages To Render applies to reports, not dashboards.
Leave time for a late report
Plan the delivery before the meeting, with enough time to notice and investigate a problem. Agree who tells the manager if the pack will be late.
Have your application request the same management pack
If your application knows when the monthly figures are ready, it can request the saved PBRS job then. The reporting team keeps control of the three-page PDF and its destination; the application handles the request to start it.
When the application also maintains page selections, keep their business meaning visible. In our example, pages one, two and three mean Summary, Sales and Operations. That relationship needs a review whenever the report author moves or replaces a page.
API example: save the three-page selection
For a supported Power BI report schedule, this fragment selects the first three pages. It is part of a schedule definition, not a complete API request.
{
"RenderingSettings": {
"PagesToRender": "1,2,3"
}
}Follow the PBRS rendering guide for the appropriate source-specific update. Preserve the existing schedule ID, recurrence, filters, other rendering settings and complete destination collections, including their identifiers.
PagesToRender uses one-based page numbers; an empty string selects all pages. PBRS visual-data export uses a separate zero-based page index. Do not copy that index into this field.
Read back the saved configuration and test the resulting PDF. The fragment does not set the reporting month, PDF format or recipients; those remain part of the complete job.
API example: start and monitor the saved pack
Use an authenticated connection and an existing single-report schedule that has passed the preview and delivery test. Replace the illustrative ID and connection values below.
POST {pbrsBaseUrl}/api/Schedule/ExecuteScheduleAsync
Authorization: bearer {pbrsAccessToken}
Content-Type: application/json
{
"ScheduleType": "report",
"uniqueid": 101,
"RunBy": "Monthly management pack"
}
GET {pbrsBaseUrl}/api/Schedule/GetExecutionStatus?ExecutionId={ExecutionId}
Authorization: bearer {pbrsAccessToken}Keep the returned ExecutionId with the reporting month. Follow the PBRS execution guide to monitor within a deadline and inspect the parsed ResultJson. Completion alone does not establish successful delivery.
If a request times out, investigate the existing run before starting another. Check the delivered PDF as well as the execution result, so a successful job does not conceal an outdated page selection. These examples have not been run against your environment.
Review the selection after a redesign
If Sales moves from page two to page four, the saved numbers may select different content. Make the management PDF part of the report author’s release check.
Start the next review with everyone on the right page
At the next review, your manager opens one PDF and starts with the overall result. Sales supplies the detail, Operations gives the team its next discussion, and the internal diagnostic page stays with the reporting team.
Start with those three checked pages and one test delivery. For the wider setup, explore scheduled Power BI PDF delivery and Power BI Report Automation. A pack your manager already finds useful is a good first job to automate.
Use the evaluation guide to plan the trial around your next management review.
Contributors:
Christian Ofori-Boateng
CEO, ChristianSteven Software
