Forum Discussion
Error Exporting Power BI using Power Automate using RLS
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.
- Anonymous4 years agoNot applicable
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
- Anonymous4 years agoNot applicable
Hi Anonymous
I find some offical blogs about export Power BI Report by Power Auto.
For reference: Row-level security in Power Automate
Video: Send Report Email By RLS in Power BI using Power Automate
Best Regards,
Rico ZhouIf this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- Anonymous4 years agoNot applicable
Thanks Rico for your link.
I have already these options, and it works fine when "identities UserName" and "user running Power Automate" are the same but it fails when I want to run Power Automate for some other user, who has RLS setup and the source is AAS.
I think solution could be using Service Principal along with CUSTOMDATA, I will try this only the proper tenant-level access is granted to Service Principal.
However, I was looking for some example who has implemented this logic.
Thanks
Ritesh