Forum Discussion

tespinal's avatar
tespinal
Frequent Visitor
9 years ago
Solved

row level security

Good Afternoon,

I was testing out RLS with my supervisor today. I added her to my role and checked to verify everything was working. I then removed her from the role and everything errored out. I assume that make sense because my guess PBI was viewing it as this person can no longer view the dashboard. I then removed her from sharing, then reshared the dashboard and she still couldn't see the dashboard. I then pulled the whole dashboard down and republished it, and she still couldn't see the dashboard. Finally, I pulled the dashboard down, delted the role, and republished, but she STILL couldn't see the dashboard.

 

Can anyone explain what is happening?

 

I tried sharing the same dashboard with another user to see if sharing was the issue, but everything worked when I shared with the new user. 

 

Any help would be appreciated!

  • Update:

     

    I was able to solve the problem by pulling everything down from the affected report from Power BI online (dashboard, report, and dataset). When I republished the report after doing that, everything worked as normal. 

  • Anonymous's avatar
    Anonymous
    9 years ago

    tespinalexactly right. No role = no data. No-filter role = all data. Filtered role = filtered data.

10 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    After publishing,  you have to go to the dataset's Security settings and add each user to their role there. Sharing alone is not enough with RLS.

    • tespinal's avatar
      tespinal
      Frequent Visitor

      Thank you for the feedback. My issue is when I wanted to remove her from the role and grant her full access again. When I tried to reshare the dashboard, it didn't let her see anything. 

      • Anonymous's avatar
        Anonymous
        Not applicable

        If you aren't assigned any role you won't see anything.

  • tespinal's avatar
    tespinal
    Frequent Visitor

    Update:

     

    I was able to solve the problem by pulling everything down from the affected report from Power BI online (dashboard, report, and dataset). When I republished the report after doing that, everything worked as normal.