Forum Discussion
Issue with new Paginated Report Visual when Embedded
I'm not sure when they added the fix - but in order for a paginated visual to work with embed you need to create a multi-resource authentication token. We are using this in our application for it to work.
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.
I agree this looks not supported at the moment on embedded, Maybe you could log a ticket.This may be supported in future release probably. However with embedded I could do this earlier with using both pbix and Paginated seperately within 2 frames on a single page, pasing selected thereby creating a visual experience similar to current Paginated visual. Both pbix and paginated being filtered using query params.
I think a good practical use case would be a detail listing table within the same page as PBI visuals. As the user clicks on summarized data (what tabular does best) related detail rows in exportable form can come up with well formatted for print data (what paginated and SQL does best). While the embed application could pick up on clicks within PBI, I think it's easier development if it didn't need to be aware of those interactions.