Forum Discussion

Kuladeep's avatar
Kuladeep
Icon for Advocate II rankAdvocate II
5 months ago
Solved

User with VIEWER role cannot see reports connected to Direct lake semantic model

Dear Fabric community,   We are facing an issue that users with `Viewer` role in Workspace unable to see any visuals from reports connected to Direct lake Semantic Models (SM). But `Contributor` ab...
Need Help
  • Kuladeep's avatar
    Kuladeep
    3 months ago

    Microsoft's suggested solution is to use 'App-Owned Data' rather than 'User-Owned Data'. This method eliminates the need for users to have access to the lakehouse in DirectLake mode, as a service principal provides access between the lakehouse (LH) and semantic model.

     

    The disadvantage is that this solution only works with web apps (as it is a Power BI embedded report; app-own-data). If the user tries to access the same report from the Fabric portal, they will encounter the same issue. 

Kuladeep's avatar
Kuladeep
Icon for Advocate II rankAdvocate II
4 months ago

I am facing one more issue since then: (I suspect because of the Data access role API)

Someone in the workspaces occasionally gets the below errors when trying to access reports or semantic models. Regardless of their role (Admin or Viewer), they continue getting these errors until someone manually refreshes the semantic model.

The users experiencing these issues are not in the workspace where I used:

/{workspaceId}/items/{lakehouseId}/dataAccessRoles?dataAccessRoleConflictPolicy=Overwrite

but in other workspaces.

Did I make any irreversible changes to OneLake?

 

errors: