Clarification on Reliability of Multi-Page Bookmark Capture in Power BI Embedded ExportToFile API

[pdixit]

We are using Power BI Embedded with the JavaScript SDK and ExportToFile REST API to generate PDF exports from reports while preserving the user's locally applied filters and runtime state.

Current implementation:

const capturedBookmark = await currentReport.bookmarksManager.capture({ allPages: true });

Then passing the captured bookmark state to ExportToFile API:

{ "format": "PDF", "powerBIReportConfiguration": { "defaultBookmark": { "state": "<capturedBookmark.state>" } } }

Our reports can contain multiple pages (commonly 6–10+ pages), and users apply filters/slicers dynamically in embedded view mode before export.

We would like confirmation from the Power BI product team regarding the following:

1. Is bookmarksManager.capture({ allPages: true }) officially guaranteed to preserve state consistently across all report pages during ExportToFile PDF rendering?

2. Are there any known limitations or “best-effort” behaviors for:

   • multi-page/ALL page bookmark capture

   • applied filters & slicers

   • drill state

   • visual interactions

   • large bookmark payloads

   • Is there any documented or recommended limit for:

     • number of pages

     • bookmark state size

     • complexity of report state

     • Is Microsoft’s recommended approach for reliable PDF export:

       • a single report-level bookmark using allPages: true

       • page-level bookmarks

       • reportLevelFilters instead of bookmarks

       • another recommended pattern

       • If allPages: true is not fully deterministic for ExportToFile scenarios, is using:

         await currentReport.bookmarksManager.capture({ allPages: false });
         

         with page-specific export configuration considered the recommended and more reliable approach?

         We found official documentation describing bookmark capture and export usage, but we could not find explicit clarification on reliability guarantees for large multi-page reports.

         Any confirmation, guidance, or known limitations from the product team would be very helpful.

[v-menakakota]

Hi @pdixit ,

Thank you for contacting the Microsoft Fabric community forum.

Thanks for sharing the detailed questions. Since this involves product behavior, reliability guarantees, and possible limitations around Power BI Embedded bookmark capture and ExportToFile API scenarios, it would be best to raise a Microsoft Support ticket for an official confirmation from the product/support team.

Please include all the detailed questions, implementation details, and any observed behavior in the support request so the team can validate.

To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Best Regards, 
Community Support Team

[v-menakakota]

Hi @pdixit ,

Could you please confirm if the issue has been resolved after raising a support case? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.

Thank you for your understanding and assistance.

Best Regards, 
Community Support Team.

[lbendlin]

We would like confirmation from the Power BI product team regarding the following:

This here is a public forum where users help users.  For these kind of questions you would need to engage your Microsoft CSAMs, DSEs or whatever they call themselves now.