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,
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!
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
Hmm that sounds like it could work out to be a solution in the end. Do you know if it's possible to switch from 1 account type to another? Or how I can recognise which account type that e-mail is?
Unfortunately I don't know...
I discovered this on accident because I had shared my report with both types of groups and one group saw it and the other one didn't. My colleague manually added / created a new group to the users from that didn't work and now everything works fine for now.
Hope you figure it out!
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...
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?