Paginated Report fails to run with embedded control in app, but works fine as a standalone option.

[tommy_g]

This is presumably a permissions issue. We publish an app which is shared for access by other users in our tenant. This works fine. 

Previously we would also publish related RDL content, also working well.

Recently we started to embed them in the PBIX reports. This works very well in my development environment, even considering we're only two months into GA.

I get the following error when accessing via the end-user account. RDL works fine. Embed in PBIX fails. 

[v-xulin-mstf]

Hi @tommy_g

Is your data source GA?

Please refer the following link about steps to embed a paginated report, please refer to the specific steps and check.

https://docs.microsoft.com/en-us/power-bi/developer/embedded/embed-paginated-reports?tabs=organizati...

If you still have some question, please don't hesitate to let me known.‌‌

Best Regards,

Link

Is that the answer you're looking for? If this post helps, then please consider Accept it as the solution. Really appreciate!

[tommy_g]

I followed the steps in the referenced article. The report runs in PPU by itself, no problem. It connects via a Live connection to a certified dataset in the same workspace. It runs fine embedded in the published app within my development account. It fails when shared to another user's PPU within our Azure tenant. Therefore I do not think it is a capacity or configuration or data source problem. Everything else in the published app works as designed.

My guess is there is a permissions issue related to embedding via the new Power BI custom control.

Searching for troubleshooting help is difficult because this is not PBI "embedded" in the traditional sense. (behind the scenes, maybe). It is strictly with running the report inside the PBIX.

[tommy_g · Accepted solution]

Problem summary: it looks like Paginated Report RDL content honors security applied to the published app, as expected. The unexpected glitch as then when the report is embedded on a PBIX report page, the permissions are NOT inherited.

Workaround: you must explictily apply sharing permissions to the RDL file.

[Anonymous]

"Workaround: you must explictily apply sharing permissions to the RDL file."

How do you do that?