Forum Discussion

juanjoseblancob's avatar
juanjoseblancob
Frequent Visitor
7 years ago

Slicer values with row level security

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...
Need Help
juanjoseblancob's avatar
juanjoseblancob
Frequent Visitor
7 years ago

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 :(

 

Thanks in advance for your follow up.

 

Juan

juanjoseblancob's avatar
juanjoseblancob
Frequent Visitor
7 years ago

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

 

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

 

Cheers,

 

Juan

  • v-yulgu-msft's avatar
    v-yulgu-msft
    Microsoft Employee
    7 years ago

    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

    • TheGoochIsLoose's avatar
      TheGoochIsLoose
      New Member
      7 years ago

      I'm coming to this conversation late, but I'm hoping someone can enlighten me on how to work around it.

      In our case, similar to the original poster, we have a subset of data that is responsive via RLS to the authenticated user. There is a single-select slicer that lets the user choose subset data within the RLS data they have access to. However, when the PBIX is published and shared, whatever option was selected at the time is saved as the default.

      Client X (given the earlier example) should not be aware of Client Y's data subsets.

      So, if this is by design, how do I make sure that a slicer gets refreshed before being displayed to the end-user? The only solution I have found so far is to turn off single-select, and clear all the checkboxes before publishing the PBIX. This is not preferable, since only one item should be chosen at a time.

      Is there any "on-load" functionality, or ANY functionality that would force a refresh of the slicer and visuals after RLS is applied?

       

      Thanks,

      R. Gooch

      • Anonymous's avatar
        Anonymous
        Not applicable
        3 years ago

        Hi! The approach I use is to add a guiding dummy row that all RLS's have access to that say for example "Please, select a customer". 

        I select that option on the slicer before saving and publishing the report. 

         

        I know this is an old question, but I came across it while looking for answers to a different question about slicers. Figured I'd leave a workaround for you  🙂