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.
Like what everybody is replying: The problem still exists. But is there any development in this issue at the moment? Can we expect a fix soon?
Do somebody know this? Please share.
Hi AlexNL ,
Since this is an knonwn issue from Microsoft end , as of now the team has suggested to follow the below approach :
" To fix the issue, customer can remove CROSSFILTER and USERELATIONSHIP from their measures. Alternatively, customer can modify the relationships as per public documentation recommendations for RLS models.
Active vs inactive relationship guidance - Power BI | Microsoft Learn
Dynamic row-level security with Analysis services tabular model - Power BI | Microsoft Learn
USERELATIONSHIP function (DAX) - DAX | Microsoft Learn
If the customer is reporting the issue accessing PowerBi reports with error:
"The USERELATIONSHIP() and CROSSFILTER() functions may not be used when querying 'T' because it is constrained by row-level security".
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.