401 error

What I can suggest is to first impersonate the role (Test as Role) of the people seeing this error and see if you are getting the same. If you are then revist your model and see if any of the relationship's has changed from single to both or are there are any breaks there and Test as Role for the users experiencing this on PBI Desktop too. That usually is where I have found my errors to be at and it has always resulted in success!

Does RLS works for the option "Hide all rows"?

Can you please ellaborate the 'Hide All Rows' option a little more so that I can understand what you are referring to?

I tested as their role and I can see the error what they are facing.

I cant figure whats the use of "relationships single or both".



Hide all rows:

When we normally start applying RLS filter, we go to Manage roles, click on the ellipse of the table, we see an option called hide all rows.

Now I have customer info, I want few people shouldn't see the email address info.
Is there any way to do it?

So this is the data, I want few pwople in the workspace shouldnot see the email address and can see everthing they wnt.
How can I do that.

Please let me kow if you want the data in excel format?

That would be helpful if you can share it in excel.

I am sorry, I can do this.
Please let me know if I can restrict the email address column

Also, just to confirm your statement for "few pwople in the workspace shouldnot see the email address and can see everthing they wnt." do you mean if [email protected] logs in he can see only row 3 and nothing 

OR

Ram can see all rows and data but cant see all of the values in CustomerEmail?

Unable to share it in excel, getting some error.
Please let me kow if you can help me out from this.
I want the column to be restricted

If you want data in a COLUMN restricted and not the ROW level data that wont be possible in a straight forward manner. As the name suggests its ROW- Level Security and not COLUMN. What I would do if it works with you is to remove the column that you want the restriction on from the first visual, and have that column adjacent to the first visual and have row level on that second visual. That will work. Maybe try that.

How do we do that?

I dint get the point "column adjacent to the first visual and have row level on that second visual. " 

Visual 1 will NOT have the column you want restriction onDefine RLS on the secondary table that contains the restricted columnDummy Data for secondary table containing the supposed restricted columnRelationship between both

This is what I came up with, you will have to change things obviosuly based on your requirement and also this is just a starting point and the only way I thought you can achieve this, you will have to break the column that needs the restriction upon and apply RLS on that column and make sure no relationship is defined between these two tables else the RLS will trickle to the other table as well.

Not a perfect solution but I think this should be a good starting point.

I am doing as direct query by using a view from SQL, how can I do this visuals at that time?