Error: The report can't be viewed because the underlying dataset uses row-level security (RLS).

[sampatreddi]

Getting the following error to random people for a couple of hours.

Error: The report can't be viewed because the underlying dataset uses row-level security (RLS)

The underlying dataset is an Azure analysis tabular model with a live connection and row-level security is not enabled on this. 

I was wondering why we are getting this error without any RLS on the dataset. 

Can anybody help, why this is happening and how to avoid in future?

Thanks in advance

[v-yangliu-msft]

Hi  @sampatreddi ,

Can you check again whether the data source Azure analysis tabular model has RLS enabled, because the mode used is live connection, and the data source Azure analysis tabular model also supports the configuration of RLS, in this case the RLS of the data source may affect the data situation when the customer uses the AAD account to send a query to view the report.

Best Regards,

Liu Yang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

[sampatreddi]

@v-yangliu-msft We haven't enabled RLS on the data source. Moreover, we faced the issue for a few hours only and the report is working fine now. Just wanted to know the reason for this intermittent issue. We faced this issue earlier also.

[v-yangliu-msft]

Hi  @sampatreddi ,

Please upgrade your gateway to the latest version.

Update an on-premises data gateway | Microsoft Learn

Reference:

The report can't be viewed because the underlying dataset uses row-level security(RLS)

Solved: The report can't be viewed because underlying data... - Microsoft Power BI Community

Solved: The report can't be viewed because the underlying ... - Microsoft Power BI Community

Best Regards,

Liu Yang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[sampatreddi]

@v-yangliu-msft Connecting to the Azure analysis tabular model doesn't require data gateways. Hence upgrading the data gateway is out of option.

The other thread doesn't give a clear picture of why this is happening.