Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Creating an embed token for Power BI today is a complex task, as not only a report may have to be embedded, but the report may use datasets from different workspaces, DataMarts, DataFlows or may embed paginated visuals etc.
Unfortunately, it is not possible to get all required information to embed a certain report by an API.
An example is embedding a Power BI report, which contains a paginated visual (technically that is a paginated report (RDL) shown within a Power Bi report (PBIX)): https://learn.microsoft.com/en-us/rest/api/power-bi/embed-token/generate-token#example-of-generating-an-embed-token-for-a-power-bi-report-with-a-paginated-visual.-the-paginated-report-id-('...4850')-of-the-paginated-visual-must-be-included-in-the-'reports'-section-of-the-request.
This requires the information about:
Provided by the Power BI REST APIs will be:
While there is a REST API to get all reports in a workspace (or organisation), including the paginated reports itself, there is no REST API providing the relation between Power BI report and Paginated report.
Please enhance the report APIs to provide all required information to create also a complex, multi-access token as described in the GenerateToken method (see examples: https://learn.microsoft.com/en-us/rest/api/power-bi/embed-token/generate-token#examples)
Regards,
HerrB@S-Com
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.