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.
The solution is not accepted because it is not a solution.
Please beware this is a very serious issue. We are talking about security and functionality that was working for years. You cannot just say that the functionality is changed and therefore all models have to change. This is fundamental. So please.... fix this bug(!)
Hi AlexNL ,
Thank you for bringing this to our attention. We understand the importance of this functionality and the impact it has on your workflows.
We want to assure you that this is a known issue is currently under investigation. support team is actively working on it, and it was considered as a high priority. We sincerely appreciate your patience and understanding.
Hi v-aatheeque ,
can you give us an estimate in which time we can expect a solution? The solution should be directly available as it was working the previous versions. Why not apply a rollback untill the latest version is fixed?
Hi,
This is again a non-solution. Removing the UseRelationship function from your measure without replacing it with something else will return other results. Can you verify if TREATAS is accepted as a valid replacement for these cases? Or will this cause similar issues?
I dont know if TREATAS is an valid replacement from Microsoft, but in my models have switched to TREATAS and it seems to work as UseRelationship used to work before. (No error messages or changed behaviors).
MarkDenHeijer Can you please send the syntax for this replacement? I am not sure if I understand it correctly. THANK YOU
Hi v-aatheeque
Is there any news?
Hi AlexNL ,
Thank you for following up. we wanted to provide an update that the issue is still under investigation and has not yet fixed.
We sincerely appreciate your patience and understanding. we will keep you updated with any progress.
Is there any update on the investigation and when we can expect a fix?
