Forum Discussion
RLS Not Working
zanottiluca Pretty sure you do not want Both. You want the relationship direction to be defined as:
Employees 1 -> * History
Thus, security enforced on Employees limits the rows and this then flows to the History table via the relationship.
zanottiluca Pretty sure you do not want Both. You want the relationship direction to be defined as:
Employees 1 -> * History
Thus, security enforced on Employees limits the rows and this then flows to the History table via the relationship.
Thanks a lot Greg_Deckler for this, this is now working, hence my error was mainly on assuming the "Apply security filter on both direction" was ticked. I mistakenly thought was a minimum requirement for DRLS to work!
Back to basis this tick and the Both direction, are needed only in case I have a bridge table inbetween employees and history which otherwise will not propagate the filter acordingly, correct?
Many thanks for this.Luca
zanottiluca - Right, the Both direction is if you would want History to filter Employees as well as Employees to filter History. To understand this, think of this scenario.
Place the "Employee" column from the Employees table in a table visual. Place a column from History in the same visual. Make the aggregation "count". You will get a count of the rows in the History table for each Employee.
Now, create a table visual with the "Employee" column from the History table in a table visual. Place a column from Employees table in the same visual. Make the aggregation "count". You will get a count of ALL the rows in the Employee table for each Employee.
This happens because Employees table filters History but not vice versa.
Thanks Greg , this indeed anwsers also to my DLRS question.
Cheers
Luca
