Forum Discussion
Performance Optimization for Power BI Row Level Security Model
Hi sumanthkakarla,
We sincerely apologize for the inconvenience caused.
As the issue remains unresolved, we kindly request you to raise the matter at Issues - Microsoft Fabric Community for investigation. Alternatively, you may raise a Microsoft support ticket using the link provided below. They will be able to offer specific insights related to your account and potential resolutions.
Microsoft Fabric Support and Status | Microsoft Fabric
If you find our response helpful, we would appreciate it if you could mark it as the accepted solution and provide kudos. This will assist other community members who may be facing similar queries.
Thank you.
Hi sumanthkakarla,
In the current configuration, the filter flows from CLIENT_LOOKUP to client_account_bridge, thereby allowing all data to pass through unrestricted.
In my view, the issue arises due to the direction of the filter. It should flow in the opposite direction from client_account_bridge to CLIENT_LOOKUP in order to effectively enforce Row-Level Security (RLS) restrictions.
By setting the cross-filter direction to Both and applying RLS on the client_account_bridge table, end users will be able to view only their assigned accounts. Meanwhile, internal users with full access will be able to view all data without any limitations.
If you find our response helpful, we kindly request you to mark it as the accepted solution and provide your valuable kudos. This will assist other community members who may have similar queries.
Thank you.