Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
Here is the bug report Super User Idrissshatila wanted me to post in this channel:
MAJOR bug as reported in thread: https://community.fabric.microsoft.com/t5/Service/RLS-and-USERELATIONSHIP-problem/m-p/4367418
RLS and USERELATIONSHIP / CROFFILTER problem.
Crucial reports all over the continent are bugging out.
According to user, 11 pm Swedish CET+1, everything worked fine, but suddenly this error occurs:
Error message example:
"The UseRelationship() and CrossFilter() functions may not be used when querying ‘TableA’ because it is constrained by row-level security defined on ‘TableA’ or related tables"
Another bug report for same issue:
https://community.fabric.microsoft.com/t5/Service/Sudden-RLS-and-USERELATIONSHIP-problem/m-p/4367400...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
These problems arise by design. As mentioned in the public documentation, USERELATIONSHIP cannot be used when defining row-level security for tables containing metrics, and CROSSFILTER is not supported in DirectQuery mode when used in computed columns or row-level security (RLS) rules.
USERELATIONSHIP function (DAX) - DAX | Microsoft Learn
CROSSFILTER function - DAX | Microsoft Learn
To resolve this issue, CROSSFILTER and USERELATIONSHIP can be removed from their metrics.Alternatively, the relationship can be modified as suggested by the public documentation of the RLS model.
Best regards,
Albert He