Paginated report visual inside embedded report RLS issue

[andjegor]

I need assistance with embedding a Power BI paginated report within a Power BI report as a paginated report visual, which is itself embedded on a platform. The paginated report is based on a Power BI dataset, which is the same dataset used by other reports embedded in the platform. This dataset has Row Level Security (RLS), and I need the paginated report to apply the same RLS as the rest of the dataset.

We are using a Power BI Premium per capacity workspace where all datasets and reports are based for embedding. I have the JavaScript code, and I need guidance on where and how to make the necessary changes to ensure the paginated report works correctly with the RLS.

Additionally, we use AWS Secrets Manager to manage the report, dataset, and workspace IDs. When a client logs into the platform, we capture their username (GUID) and match it against a Redshift table to determine the appropriate data access.

In general, above scenario is possible to achieve?

[andjegor]

I think, I need to be a little bit more specific about my issue.

Current set up:

1. JavaScript code that generates access token for embedded solution.

2. AWS secret manager to specify workspace, dataset and report ids.

3. Power Bi dataset published in premium capacity workspace (call it "XYZ")

4. Power Bi dataset has RLS applied

5. Report (call it "XYZ123") that connects to Power Bi dataset "XYZ" is embedded to the platform. All working fine.

6. Then I created paginated report using dataset "XYZ" as a source in Power Bi Report Builder.

7. Paginated report from point 6 is published in the same workspace as dataset "XYZ" and report "XYZ123"

8. Opened report "XYZ123" and insert paginated report visual. As a source for the visual, using paginated report from point 6.

Result - everything is working, except paginated report visual. Error message just saying "Unexpected error".

If above set up is possible to achieve in embedded environment? what I am missing? is it a code change?

[Anonymous]

HI @andjegor,

What type of embedded mode are you worked on? Have yo checked the document limiting part that I mentioned above if your scenario meet to these?

Regards,

Xiaoxin Sheng

[lbendlin]

This may help

Use row-level security when embedding paginated reports - Power BI | Microsoft Learn

[andjegor]

No, I checked MS documentation, and it's not working. Userid is not passing to paginated report.

[lbendlin]

If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .

[Anonymous]

Hi @andjegor ,

Did the above suggestions help with your scenario? if that is the case, you can consider Kudo or Accept the helpful suggestions to help others who faced similar requirements.

Regards,

Xiaoxin Sheng

[Anonymous]

Hi @andjegor,

For use RLS with power bi embedded, you can check the official document if helps:

Use row-level security when embedding paginated reports - Power BI | Microsoft Learn

Regards,

Xiaoxin Sheng

[andjegor]

No, I checked MS documentation, and it's not working. Userid is not passing to paginated report.

[lbendlin]

You say "issue"  - have you encountered an actual issue?  RLS will work based on the effective UPN, regardless where that is coming from.

Are you sure you want to subject your customers to such a multi-embedding scenario? Is the UX acceptable?

[andjegor]

Hi Ibendlin

Yes, when I said "issue", that means my current set up isn't working, resulting in error. No specific error message. Problem is that username is not passing to paginated report.