Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
7 years ago
Solved

Row level security doesn't work when using 'Both' cross filter direction

We are trying to apply Row Level Security (RLS) using Power BI RS using the January 2019 Release that now supports it.  The security filter doesn't cross filter to the transactions.  I have a securit...
Dynamic RLS
Row Level Security
  • rpatkar's avatar
    rpatkar
    7 years ago

    We have issued a fix for this issue in the latest build 15.0.1102.235. Please upgrade to the latest build available.

    Thanks,
    Rohit

praseejbk's avatar
praseejbk
Advocate I
7 years ago

Hi

 

I am presently using PBIRS january - 2019 version also using January - 2019 Desktop version. I tried RLS which is not working for me. I used a colmn with User Names and  in Manage Roles [User Name] = USERNAME() in order to filter base on the user names. when I try view as roles it work fine. but in server nothing filtered. configuration of PBIRS as Manage-> row level security -> add member.

 

if any one tried and success please let me know.

 

Regards

Praseej   

Mithrilendil's avatar
Mithrilendil
Frequent Visitor
7 years ago

Hello,

 

Desactivate RLS on your report, add a measure with username() formula and publish the report to see what username() looks like.

 

On desktop (in my environment) the result of username() is DOMAIN\login and on the server it is [email protected]

  • Anonymous's avatar
    Anonymous
    Not applicable
    7 years ago

    I'm seeing the same behavior as Anonymous. I've confirmed that the filter he's setup (using USERPRINCIPALNAME()) is correct, but irrelevant to the issue.

     

    Removing the security filter on the relationship between Responsibilities and Cost Centres (and ensuring the proper UPN exists in the Responsibilities table) allows the upload to succeed. I can see the Responsibilities table filtered as expected, but then the other tables naturally aren't filtered.

     

     

    • rpatkar's avatar
      rpatkar
      Power BI Team
      7 years ago

      We have issued a fix for this issue in the latest build 15.0.1102.235. Please upgrade to the latest build available.

      Thanks,
      Rohit

      • Anonymous's avatar
        Anonymous
        Not applicable
        6 years ago

        We are still encountering same error in Power BI Desktop Version: 2.76.5678.782 64-bit (December 2019)

        Is this resolved? if yes the how.. please share the step(s).

         

         

        Thanks