Forum Discussion
PaginatedReportEmbedForbidden: Embedding Paginated report in BI report
Hi rludwig21 ,
I believe the issue is related to the way you are generating the embed token. There are 2 endpoints for generating an embed token, and the one which you should be using for your case is the newer one which generates a token for multiple resources (because you have a paginated report inside a Power BI report).
Please see this example for how the generate token request should look like: Embed Token - Generate Token - REST API (Power BI Power BI REST APIs) | Microsoft Learn
Thanks,
Amos
Community SupportHi rludwig21 ,
It seems that you are using A1 SKU? Embedding Paginated Reports on Generation 1 required at least an A4 SKU and with Gen 2 you can embed paginated reports from A1 SKU onwards. Please check which Power BI embedded Generation are you using.
Besides, here are some considerations and limitations :
Considerations and limitations of Embedded paginated reports - Power BI | Microsoft Learn
Best Regards,
Jianbo Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thank you Jianbo,
We are using a Gen2 as mentioned above and I have read through the limitations but nothing appears to be out of place. I can actually embed a the paginated report by itself fine, just not inside a BI Report. Real Problem is parameters/filters cannot be passed via JavaScript to the paginated reports which is a requirement for my company. Hence why I'm using a Power BI Report with the pagninated report within the BI report as it can be used to do so only this way.
It works fine as shown here in the dev sandbox and parameters pass as shown below from the sandbox.
Just not sure why mine is getting blocked... we are paying for the A1 SKU (Gen2) assigned to the workspace: