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#M261685
11 Comments
Hi robertnorman ,
The product team has taken note of the situation and is working on it, if there are any new developments I'll reply below.Best regards,
Albert HeIf this post helps, then please consider Accept it as the solution to help the other members find it more quickly
Hello,
Can you give us an update? Or an estimation regarding the time needed to solve this issue? It is near closing time for Fiscal Quarter and all people want to access the dashboards and can't.
This issue is like the Crowdstrike, but for PBI.Since this is the PBI support team, I would say between 12 hours and 12 years 🙂
Anonymous : Thanks for investigating!
Any news if this change in the service is reverted anytime soon.
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?well at the end it did seem that is a bug, glad you posted it here so everyone could relate to.
Can we get an update on this, please? This is impacting many users.
Any news? We are on stand by waiting to check if this is going be to fixed or if we need to update hundreds of measures that are broken now in our reports...
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 LearnTo 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- So to summarize - you broke existing functionality, said you will investigate, failed to fix it and called it existing functionality. Thanks for the hard work and support!
- I am getting problem in power bi desktop, when i click to open the save files its always buffering and displaying working on it .
