Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
Sudden (for me 16/01) problem with RLS and USERELATIONSHIP on long existing reports.
See also https://community.fabric.microsoft.com/t5/Service/RLS-and-USERELATIONSHIP-problem/m-p/4362965
@ju97 , @dhoskins , @idrisshatila
A large amount of visuals on existing reports are impacted !
Hi @ElsDEs, Hope your issue is solved. If it is, please consider marking it 'Accept as solution', so others with similar issues may find it easily. If it isn't, please share the details.
Thank you.
Hi @ElsDEs, Hope your issue is solved. If it is, please consider marking it 'Accept as solution', so others with similar issues may find it easily. If it isn't, please share the details.
Thank you.
Hi @ElsDEs, Hope your issue is solved. If it is, please consider marking it 'Accept as solution', so others with similar issues may find it easily. If it isn't, please share the details.
Thank you.
As this could take a while on MS side:
Especially our complex models rely heavily on USERELATIONSHIP() as it seems the most performant way, to handle down long (snowflake) paths.
Would TREATAS() from the RSL-Dim-Table to the other tables be a full replacement instead of all those (inactive) relationships? -> ScreenshotRLS -Example where the plant feeds into many different Dims and Facts
Any experiences already before we take this huge effort of rebuilding?
Especially performance impact on an anyway already complex fully multilingual report...
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
Hi @ElsDEs , thank you for reaching out to the Microsoft Fabric Community Forum.
Please consider reaching out to Microsoft Support. You can provide them with all the troubleshooting steps you've already taken, which will help them understand the issue better and provide a resolution. They might be able to identify something specific about your admin account setup or provide a solution that isn't immediately obvious.
Below is the link to create Microsoft Support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
If this helps, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details.
Thank you.
Same here : many production clients reports affected.
How is possible to do that without announcing it ?!!
@Microsoft please go back, at least for some days, in order for us to adapt the reports.
We are facing this issue as well .
Same issue for all my curstomers..
I have a customer with the same issue. They are using the January 2025 version of Power BI desktop, and things broke out of the blue.
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.
This is a bug introduced by Microsoft for security tightening.
Hmmm. That should have been announced before release so that people have time to adapt their models. We are going to lose many days of work and end user trust on business critical reports due to this 😞
We are experiencing a similar issue with Row-Level Security (RLS) and the USERELATIONSHIP function, which has significantly impacted a substantial number of visuals in our long-standing Power BI reports. This disruption began on 16/01 and is directly affecting critical dashboards on all environments.
If Microsoft or others have insights on how this issue has been resolved, we would greatly appreciate hearing about any solutions. Thank you for your continued support in addressing this critical matter.
Thank you
Ganesan Muthiah
We have the same issue. Seems to have appeared all of a sudden on a report which wasn't an issue before.
Same issue, is affecting crucial report. Please fix ASAP.
User | Count |
---|---|
48 | |
28 | |
21 | |
19 | |
19 |
User | Count |
---|---|
51 | |
47 | |
25 | |
23 | |
20 |