Hey guys & gals, I've been experiencing some issues sharing an app with one of my colleagues today. He has access to the app, and is able to view it, but all the content is missing behind errors. Now I recognized this as "this person is not a member of the workspace", it looks very similar to that. But even after adding him to the group as a member, he still sees this error. I have admin access to the workspace, but I'm at a loss to figure out how to make sure this person has access. Is anyone familiar with this problem? When I searched for this exact error message, literally nothing came up, which seems very strange... Thanks for thinking along, Jaap

I've have had the same issue... For me the solution was to go to the RLS (Row-Level Security) settings (in the online version) on the datasets via the three "..." In the RLSview you'll have to choose every single person you've shared the data with and enter their e-mail once again, and press "Add" and then "Save" in the buttom. I hope this is useful for others - I've spend hours seaching for the solution... BestJanus

Hi Folks, I'm using Report Server (rarely use the cloud). Had the same issue with the "Visual contains...yadda..." Discovered that if I removed the Role I had setup in the IDE for testing, it worked fine once published. Figured I'd share in case it helps anyone else. Microsoft figured otherwise. Took me a while to get logged in here again. /sigh Dave

Just in case this still helps someone, I too got the same error (this visual contains restricted data) for all visuals. For me the problem was that all the RLS roles that I had defined a long time ago for completely different reports, were kind of copied to this new report. I'm calling them ghost roles, since there were no attached rules whatsoever, so they should not have had any impact. Previously I've published many different reports, which were no different from this one and which worked fine so far. The one difference with this report however is that while normally I only use a MySQL database as a source, this time I had added a new on-premises source (a folder containing (subfolders containing) .XML files). This folder was added to the gateway and my guess is that this somehow interfered with the RLS roles, even though they were empty. The solution was a simple one though, just delete all the roles in Power BI Desktop and republish. Cheers,Niels

Hi Anonymous, Please go through the below screenshot, will help you. Let me know if any issue. Thanks

I did the exact same thing as you -- removed RLS from a report that used to have it -- and now I'm also getting the error "This visual contains restricted data" I tried removing the report from the app, publishing, adding it back again, and republishing, but to no avail. Posting to subscribe to this thread in case anyone figures out a fix!

this visual contains restricted data | Microsoft Fabric Community

21 Replies

JanusPedersen
New Member
7 years ago
I've have had the same issue...

For me the solution was to go to the RLS (Row-Level Security) settings (in the online version) on the datasets via the three "..."

In the RLSview you'll have to choose every single person you've shared the data with and enter their e-mail once again, and press "Add" and then "Save" in the buttom.

I hope this is useful for others - I've spend hours seaching for the solution...

Best
Janus
- cosmoto91
  New Member
  7 years ago
  JanusPedersen wrote:
  I've have had the same issue...
  
  For me the solution was to go to the RLS (Row-Level Security) settings (in the online version) on the datasets via the three "..."
  
  In the RLSview you'll have to choose every single person you've shared the data with and enter their e-mail once again, and press "Add" and then "Save" in the buttom.
  
  I hope this is useful for others - I've spend hours seaching for the solution...
  
  Best
  Janus
  
  This actually worked for myself. I just added the user for which there were problems to all possible groups. Seems like overkill though.
  - Anonymous
    Not applicable
    7 years ago
    Hi Folks,
    
    I'm using Report Server (rarely use the cloud). Had the same issue with the "Visual contains...yadda..."
    
    Discovered that if I removed the Role I had setup in the IDE for testing, it worked fine once published.
    
    Figured I'd share in case it helps anyone else.
    
    Microsoft figured otherwise. Took me a while to get logged in here again. /sigh
    
    Dave
C4YNelis
Advocate III
5 years ago
Just in case this still helps someone,

I too got the same error (this visual contains restricted data) for all visuals. For me the problem was that all the RLS roles that I had defined a long time ago for completely different reports, were kind of copied to this new report. I'm calling them ghost roles, since there were no attached rules whatsoever, so they should not have had any impact.

Previously I've published many different reports, which were no different from this one and which worked fine so far. The one difference with this report however is that while normally I only use a MySQL database as a source, this time I had added a new on-premises source (a folder containing (subfolders containing) .XML files). This folder was added to the gateway and my guess is that this somehow interfered with the RLS roles, even though they were empty.

The solution was a simple one though, just delete all the roles in Power BI Desktop and republish.

Cheers,
Niels
zlokesh
Resolver I
8 years ago
Hi Anonymous,

Please go through the below screenshot, will help you. Let me know if any issue.

Thanks
- Anonymous
  Not applicable
  8 years ago
  The user is added there through a group membership. I checked, and the user is part of that group. Other users in that group CAN use the reports.
  
  Thanks for thinking along though!
  
  Jaap
Anonymous
Not applicable
8 years ago
I'm having the same issue with an app I published to a group.
Have you found any solution to this?

Br,
T
- Anonymous
  Not applicable
  8 years ago
  Unfortunately not :( I'm kind of hoping that the new version of PowerBI Workspaces might end up helping in this regard.
  - Anonymous
    Not applicable
    8 years ago
    Anonymous,
    
    I managed to fix it - I think.
    
    It had something to do with the kinds of groups I shared it with. Some had this errror and others didn't. On-premise AD groups had this error but Azure AD groups didn't
    
    Br,
    T
Anonymous
Not applicable
7 years ago
Hi ,

I am facing the same issue. I have removed all the RLS which was there earlier and also enabled the access as mentioned in your screenshot for users. Even after that i am getting the same error saying we do not have access to view the backend data.

Do you have any other solution for this issue?

Thanks,
Ganesan k.
- Anonymous
  Not applicable
  7 years ago
  I did the exact same thing as you -- removed RLS from a report that used to have it -- and now I'm also getting the error "This visual contains restricted data"
  
  I tried removing the report from the app, publishing, adding it back again, and republishing, but to no avail.
  
  Posting to subscribe to this thread in case anyone figures out a fix!
  - Anonymous
    Not applicable
    7 years ago
    Please click on the Datasets tab present in the power bi service along with that report. Check the security tab whether it has any RLS still showing. It has to show the below message if there is no RLS. Also specify the access level set for your role if you are member to that workspace.
    
    Thanks,
    Ganesan k.
Doby42
Frequent Visitor
7 years ago
nothing fixed it till I deleted the user out of "managed roles" from the "Managed Roles" within the power bi Desktop app. after that I replublished and it worked. Adding a user to RLS within the web under datasets got rid of the error but no data would show for the user.
Anonymous
Not applicable
6 years ago
Hi Anonymous , I am also facing the same issue. did you fix the issue? if yes pls guide me how to fix the issue.
- Anonymous
  Not applicable
  6 years ago
  Hey Mohammadr,
  
  I saw this error today, and it was caused by Row Level Security rules on the powerBI file. Did you check that your file does not have ANY RLS rules applied to it? If it has any, than all users with "viewer" permissions will not be able to see any of the data by default.