Forum Discussion
Sudden RLS and USERELATIONSHIP problem
As far as I'm aware TREATAS is the same as CROSSFILTER and isn't supported for RLS so this won't work. I think I briefly tested it last week and found that to be the case.
We are currently reworking our model after seeing the below documentation from the end of December. It does not look like this is something Microsoft is going to change back (see Refactoring Methodology in the documentation) and the response on the other thread: Re: RLS and USERELATIONSHIP problem - Microsoft Fabric Community
Active vs inactive relationship guidance - Power BI | Microsoft Learn
Reposting from other thread for visibility:
To memory - the purpose of this error is to prevent exposing data to users which they should not see, if there is an active relationship between a dimensional table where RLS is applied, and fact tables in the model. The active relationship propagates RLS from the dimensional table to the fact table. If there was a second, inactive relationship, between the dim table and fact table, trying to enable by using USERELATIONSHIP would cause the error.
However, if there was no active relationship between the two tables (for example, two inactive relationships), USERELATIONSHIP would still work fine. I'm guessing because the lack of an active relationship means RLS is no longer propagating any filters to the fact tables. That is how my model is structured. It seems such a setup is no longer working since this bug started, and in my view, there should be no reason for that. It is almost as if any usage of USERELATIONSHIP between a dimensional table with RLS and fact table is now banned. We need this changed reverted as soon as possible, it also severely limits the usefulness of this formula.
