I have this problem: I have created a SSAS Tabular 2016 model with a role called: "ThisIsASecurityRole". This "role" use the following DAX filtering: =Users[Login]=USERNAME() on the Users table (Table columns: PK, Login). The goal is to have a second table, the TimeRecorded table, filtered by users.
I use the following connection string:
"Data Source=ServerName\InstanceName;Initial Catalog=RowLevelSecuritySSASTabular;Roles=ThisIsASecurityRole".
When I connect to Power BI using the above connection string (I amend the connection string in PBRS/Manage/Data Sources/Connection String), the Power BI report works but do not filter the data.
I've created the Power BI report using a live connection to the SSAS Tabular 2016 described above
( Home/Get Data/Analysis Service/"Connect Live"/Model) using the appropriate Server and Database names. I then saved the report on PBRS. This is the only source in the power bi report.
What steps do you think are missing in order for Power BI to filter my report according to the role called 'ThisIsASecurityRole" defined in SSAS Tabular 2016?
UP. So nobody has an answer to this query? This is the 3rd or 4th of such post - the others are created by other people - and nobody seem to know whether this is a bug or if there are way around this?
We've managed to implement this succesfully. I can't quite see what's different about what you have done and what we have done. I think they are more or less the same.
I do think you may be hitting an issue with the test account you are using. You say you are remoting onto a mahcine as that user, so it probably has fairly elevated privilages.
The info shown in the original posts includes
TextData = "*,thisisasecurityrole"
the * indicates the user is a member of the admins groups and this is probably causing your security to be ignored, hence the reason the user is seeing everything.
That exactly was the problem in my case! The administrator role supersedes all other roles, eliminating all RLS conditions.
Many thanks for pointing that out!