Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!

Reply
pntlindsay
Frequent Visitor

Role filtering vs slicer behaviour

Hi,

I am hoping someone can help.  I have a report where roles are defined based on a field called territory.

I have some values that I dont want to be filtered by territory and these are calculated as follows:

team actual = calculate(distinctcount( total sales), all ('territories' [territories]).

I have a filter based on territory and when I select a specific territory I get "team actual" as I expect, without being filtered by territory. All good so far.

I now define Roles with a filter based on Territory.  When I select a role, I now get "team actual" filtered by the territory!  Which is not what I want.  

I cant understand the difference in behaviour.  What am I missing here please?

1 REPLY 1
XLBob
Resolver II
Resolver II

My understanding of row level security is once you define a role on territories, the underlying data for the team that is based in that particular territoriy will be 'visible', anything else is not accessible due to RLS working behind the scenes.

Helpful resources

Announcements
April AMA free

Microsoft Fabric AMA Livestream

Join us Tuesday, April 09, 9:00 – 10:00 AM PST for a live, expert-led Q&A session on all things Microsoft Fabric!

March Fabric Community Update

Fabric Community Update - March 2024

Find out what's new and trending in the Fabric Community.