Forum Discussion
RLS and USERELATIONSHIP problem
Hi ju97,
Thank you for bringing this issue to our attention. We understand that the error related to the UseRelationship() and CrossFilter() functions has recently impacted your report, despite it functioning well previously.
As this is a known issue that is currently being addressed, we are unable to keep this thread open indefinitely.For official updates, you can check for more information through the provided link : Known issue - Reports that use functions with RLS don't work - Microsoft Fabric | Microsoft Learn
In the meantime, if you continue to experience difficulties, we kindly encourage you to create a new thread. This will allow us to assist you more effectively.
Thank you for your understanding, and please know that we are here to help!
Best regards,
Atheeq.
Hi ju97
The error with USERELATIONSHIP() and CROSSFILTER() in reports constrained by RLS typically arises when DAX logic conflicts with RLS rules. If the report was working fine and suddenly broke, it’s likely due to recent changes. These could include modifications to the underlying dataset, relationships, or RLS rules, as well as anomalies in source data. A recent Power BI Service update might also have altered how RLS or these functions are handled. Additionally, changes to the gateway or workspace configurations could contribute to the issue. Review the dataset, RLS rules, and data for any updates or conflicts. If no changes are identified, check Power BI release notes or contact Microsoft support for further investigation.
As reported by literally everyone else in this thread, no changes were made to underlying reports, the error appeared overnight on stable reports which had not had changes for YEARS. I was able to find a workaround as described in my other comments but it still stands that something was definitely changed from Microsoft's side, which was not described in the release notes and broke extremely critical reports. Denying this is neither honest nor helpful.
This most be the most non-answer "answer" i've ever seen. Did you actually not read the whole thread? We know what the problem is, and what we can do about it. But on my side i don't like it when a function work fine until breaking changes that WAS NOT IN THE RELEASE NOTES breaks my customers reports.
Thank you for reply but I can say by 100% certaintcy that we did not change anything in the model, data or relationships etc. Everything is exactly the same.
