Error with RLS and direct query to semantic model

[DennesTorres]

Hi,

In my scenario, I have a semantic model created from a lakehouse, let's call it MyData. It's naturally a direct lake semantic model, but I'm not expecting to use direct lake, I know it will fall back to direct query and this is not  a problem.

I have another semantic model called ReportModel which uses MyData and also other sources.

On ReportModel, I need to apply RLS.

The problem: The ReportModel works well when viewed by an admin, but when viewer by a regular user, it generates the error on the image below.

I already tried to configure the Cloud connections, but it doesn't help.

Is there a solution for this, or is this  a current limitation?

I was told that if MyData is using SQL connection instead of direct query it would work, is this true? This will be my next attempt.

Anyway, the error seems like a bug, it behaves like one.

Kind Regards,

Dennes

[Anonymous]

Hi @DennesTorres 

Verify that the regular users have the necessary permissions to access both MyData and ReportModel. Lack of permissions can sometimes cause access issues.

Best Regards,

Jayleny

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

[DennesTorres]

Hi,

The user I'm using for testing purposes has Admin access to both workspaces where MyData and ReportModel are located. It still fails.

I suspected it could be related to the fact MyData being a direct lake semantic model. I created a different one, consuming from a SQL Endpoint using direct query. The failure continues to be the same.

There is the suspicious this is caused because the lakehouse MyData is consuming is full of shortcuts. However, the targets of these shortcuts are in the same workspace and the user is already admin of the workspace.

Any additional idea?

Kind Regards,

Dennes