Forum Discussion
RLS for 3 Tier Hierarchy – Two Way Filtering
What's the point of RLS if you are filtering up? Can you challenge if RLS is actually required for your use case?
Anyway, your rule can be refactored as
USERPRINCIPALNAME() IN {
[DIVISION_USERPRINCIPALNAME],
[AREA_USERPRINCIPALNAME],
[USERPRINCIPALNAME_MANAGER]}
Yes, RLS is required based on the hierarchy that is mentioned. Actually, we have 3 different sets of visuals for Region, Area & Territory so when a terrritory manager 1101, as shown in the screenshot above logs in, he sees the same values in all 3 sets. We are looking for a solution, if possible, to reflect complete values in the higher hierarchy visuals.
So territory manager for 1101 sees his values in territory visuals, but he needs to see the complete (aggregated) values of area 'Lahore' which is made up of a total of 10 territories. So he can see the aggregarted values in Area visual but not the individual territory values. Similarly for Region.
Might be easier to use three different reports/audiences.