Embedded Paginated Reports and Apps (including Org Apps in Preview)

[JenAbe]

I have set up a few PBIX reports which successfully use embedded paginated reports as drill throughs from another visual.

However I have encountered an irritating situation when publishing those reports to an APP. Keep in mind when reading this that no one but administrators have access to the underlying workspace and rely on APP audience setup etc...to access reports.

1. In order for a drill through embedded paginated report to function in the app without giving a permission error, one needed to also publish the paginated report to the same app audience. This exposes a report that really should never be run on its own as it has hidden parameters used in the drill through process. Is there any way for the embedded paginated report to simply inherit permissions from the PBIX so that it needn't be exposed on its own via the app simply to have it able to run in the host report

2. I realize it is still in preview - but embedded paginated reports DO NOT WORK in org apps because of the above mentioned 'feature' requiring the paginated report to be published to the same app as the host PBIX. Org Apps do not support paginated reports AND if/when they do, will have the same irritating user experience issue as above

Any thoughts on these issues? Has anyone encountered this before and discovered a viable workaround? Can't hide reports added to apps obviously 🙂

Thanks!

[rpatkar]

hi @JenAbe,

Have you seen the opton to "Grant access to hidden content" at Publish an app in Power BI - Power BI | Microsoft Learn. It esentially lets you hide paginated report in your app while still giving permission to your app users.

[JenAbe]

Oh that is interesting...unfortunately though it opens up a bit of a can of worms on that front as if someone is sent a link to hidden content they are genuinely not allowed to see they can get access. I can work around it though by using seperate apps instead of audiences to limit access.

Thanks for the tip!!!!

[v-priyankata]

Hi @JenAbe,
We appreciate your efforts and are pleased to hear that your issue was resolved. Please mark the helpful response and accept it as the solution. This will assist other community members in resolving similar issues more efficiently.

Thanks,
Priyanka

[v-priyankata]

Hi @JenAbe 

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-priyankata · Accepted solution]

Hi @JenAbe 

Thank you for sharing your query with us! It looks like you’re facing some challenges with embedding paginated reports in apps, especially in the context of managing permissions and the app audience setup.

As @GilbertQ  mentioned, currently, the embedded paginated reports need to be published to the same app audience to avoid permission errors, which can expose reports that aren't intended to be accessed on their own. Unfortunately, as of now, there isn’t a native feature to make the embedded paginated report inherit permissions from the PBIX directly, without having to publish it separately to the app.

We recommend submitting an idea on the Fabric Ideas portal, as this might help the feature get more visibility and votes, which could lead to its consideration in upcoming Microsoft updates. You can access the Ideas forum here: Fabric Ideas Portal.
If this helps, then please Accept it as a solution and dropping a "Kudos" so other members can find it more easily.

Thank you.

[GilbertQ]

Hi @JenAbe 

As far as I am aware it is not currently possible. You can vote or create an idea here: https://aka.ms/FabricIdeas