Forum Discussion
Solved
Error Power BI Service - Need Help Please!
I am experiencing an intermittent behavior in the Power BI Service related to Row-Level Security (RLS) and would like to know if anyone else has encountered something similar. In some Power BI Servi...
I found this as a Closed issue on the Microsoft Fabric Known Issues page for Power BI: Microsoft Fabric Known Issues
DescriptionYou can define row-level security (RLS) for a table that contains measures. USERELATIONSHIP() and CROSSFILTER() functions can't be used in the measures. A change was recently made to enforce this requirement.When viewing a report, you see an error message. The error message is similar to: "Error fetching data for this Visual. The UseRelationship() and Crossfilter() functions may not be used when querying <dataset> because it is constrained by row level security" or "The USERELATIONSHIP() and CROSSFILTER() functions may not be used when querying 'T' because it is constrained by row-level security."Solution/WorkaroundThe change is to enforce a security requirement. To prevent your reports from failing, you can remove USERELATIONSHIP() and CROSSFILTER() from your measures. Alternatively, you can modify the relationships using recommendations for RLS models. (
https://learn.microsoft.com/power-bi/guidance/relationships-active-inactive)
I found this as a Closed issue on the Microsoft Fabric Known Issues page for Power BI: Microsoft Fabric Known Issues
Description
You can define row-level security (RLS) for a table that contains measures. USERELATIONSHIP() and CROSSFILTER() functions can't be used in the measures. A change was recently made to enforce this requirement.When viewing a report, you see an error message. The error message is similar to: "Error fetching data for this Visual. The UseRelationship() and Crossfilter() functions may not be used when querying <dataset> because it is constrained by row level security" or "The USERELATIONSHIP() and CROSSFILTER() functions may not be used when querying 'T' because it is constrained by row-level security."
Solution/Workaround
The change is to enforce a security requirement. To prevent your reports from failing, you can remove USERELATIONSHIP() and CROSSFILTER() from your measures. Alternatively, you can modify the relationships using recommendations for RLS models. (
https://learn.microsoft.com/power-bi/guidance/relationships-active-inactive)
https://learn.microsoft.com/power-bi/guidance/relationships-active-inactive)