Reply
Frequent Visitor
Posts: 12
Registered: ‎04-06-2018

Slicer values with row level security

[ Edited ]

Hi!

 

I have the following issue. My report is basically driven by a slicer with all customer names, and this works fine for those of us with access to the full data set since we choose customers on the slicer and see the data for each.

 

Now, I want to share the report with actual customers, each of which should obviously only see their data. I can essentially achieve this with Row Level Security, BUT I am facing the following: the customers slicer does not change to have as the only option the one value in the customers table that I allow each role to see, but actually it retains the "last" value the report had for the slicer (although it´s not a valid value for that role!).

 

Example to explain:

- The last value the slicer had was Customer Y (but with full access I can see all other customers in the slicer)

- I change to a role that can only see Customer X... and the charts are all empty because the slicer remains set on Customer Y, whose data this user has no access to. If I display the values in the slicer, I can see it´s only Customer X, but as a user experience is clunky (plus they see other client´s name as they go into the report).

 

By the way, I can experience exactly the same behaviour if I use URL filters (and filter by Customer X); the report is filtered to only data from Customer X, but the slicer keeps the "last value" it had.

 

Any option to "initialize" the slicer properly?

 

Thanks in advance!

Community Support Team
Posts: 5,660
Registered: ‎09-21-2016

Re: Slicer values with row level security

Hi @juanjoseblancob,

 

Please check whether this porblem exists in desktop. If yes, please re-create the RLS and check again.

1.PNG

 

I cannot reproduce the same problem on my side. Please test my sample .pbix file on your side to see if issue persists.

 

Best regards,

Yuliana Gu

Community Support Team _ Yuliana Gu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Attachment
Frequent Visitor
Posts: 12
Registered: ‎04-06-2018

Re: Slicer values with row level security

Hi Yuliana.

 

Thanks a lot for your reply, and for the sample to test. Indeed, the problem does happen in the very simple file you sent. The key aspect to test it, though, is the following:

 

  1. Select a customer on the slicer (for instance, select X) -> this is the key step.
  2. Then change to a role that doesn´t see X (for instance, change to Role 2 which can only see Y)

You will see how the slicer still keeps X! If you don´t have anything preselected on the slicer (that is, if you don´t do step 1), then all works fine... but that´s not my scenario Smiley Sad

 

Thanks in advance for your follow up.

 

Juan

Frequent Visitor
Posts: 12
Registered: ‎04-06-2018

Re: Slicer values with row level security

Hi again! I could finally get back to my PowerBI community account after all the mess with associating non-organizational and organizational accounts Smiley Sad

 

Were you able to replicate this Yuliana? Should I report it as a bug?

 

Cheers,

 

Juan

Community Support Team
Posts: 5,660
Registered: ‎09-21-2016

Re: Slicer values with row level security

Hi @juanjoseblancob,

 

 Please review the response from PG:

 

By Design. RLS causes a Table-level filter based on the role, it does not update any slicer visuals. It is an "invisible" filter applied to every query that is generated.

 

Best regards,

Yuliana Gu

Community Support Team _ Yuliana Gu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.