Forum Discussion
Paginated report embedded for your customer, RLS and CUSTOMDATA()
Paginated Reports do not have a CustomData property that can be passed on to the semantic model's CustomData property. You need to use the UserID to tunnel custom RLS information if you are using Paginated Reports as documented here Use row-level security when embedding paginated reports with Power BI embedded analytics content - Power BI | Microsoft Learn
Thanks for your answer. I have read that article and I don't quite get that part about token generation. Currently in my case UserID function retreives string like the following pattern "xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" and it displays the same for each user. What will change after token generation? UserID will retreive different values for each user? Should I generate token for each and every user? I just need to know who is logged to my custom web application. Thanks
mora11 wrote:
What will change after token generation?
You must currently be generating a token for the embedding to be work, you just need to push the value you are injecting into the CustomData into the User value for the token.
mora11 wrote:
Should I generate token for each and every user?
Yes, you should be doing this already
mora11 wrote:
I just need to know who is logged to my custom web application. Thanks
Your app should already know this as it should be doing it's own authentication. What you need to do to get the RLS to work with a paginated report is to push the value you want to use for filtering in your RLS rule into the User field so that this can be passed on from the paginated report to the dataset UserName() function.
No, the case is that USERNAME() in Paginated Reports retreives service principal id instead of user id. Built in function UserId does not recognize custom users properly.