If you have RLS in place then you can use your ONE report level filter to inject the user emai into the export request. That will then take care of the data visibility.
Be prepared for lots of agony though - exporting multiple reports will result in 429's very quickly. It's rather useless at the moment.
Hi Ibendlin
Thanks for your reply.
In my flow (which uses "Export to File for Power BI Report" action/API ), the Report Filters and RLS are applied correctly and generates PDFs but only for user who executes the flow. For rest of the user, it shows error message
Creating embed token for accessing dataset requires effective identity username to be identical to the caller's principal name.
However, I noticed yesterday that this happens only when source system is AAS otherwise it works fine other source systems.
Any suggestions? Should I use CUSTOMDATA?
Regards
Ritesh
That's not what I meant. Run the flow with high level permissions but inject the target user email into the RLS table via the report level filter.
Hi Ibendlin
Apologise but I don't understand when you say "inject in RLS table via report level filter".
Here RLS table sits in AAS.
Please correct me.
Thanks
Ritesh
