CODEWITHSUNDEEP
powerbirow-level-security
redshift489
redshift489

Reputation: 1

USERELATIONSHIP() error with RLS recently?

I have a Power BI report that's been up for months, with no problem.

Last Monday (20/01/2025), suddenly, some of the visuals are giving me the USERRELATIONSHIP() error.

The UseRelationship() and CrossFilter() functions may not be used when querying 'tablename' because it is constrained by row-level security.

It's only showing this error in Power BI service, not in Power BI Desktop (not even when I turn on "View As" in the Modelling tab). This had never happened before, only started on Monday. It's always had lots of measures with USERELATIONSHIP() in the definition, and it's always had RLS rules on.

I rolled back to a version of the .pbix file that was from October 2024, where it was fine. When I publish the October version, it exhibits the USERELATIONSHIP() error.

After doing some reading, I guess this is actually proper security behaviour. It should be erroring out. But why didn't it exhibit this beheviour until last week? Why was it "fine" before? Did anyone else experience the same?

Upvotes: 0

Views: 96

Answers (1)

hannibalmads
hannibalmads

Reputation: 1

It was a change implemented.

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/en-us/fabric/known-issues/known-issue-1002-reports-functions-rls-not-work

Upvotes: 0

Related Questions