Error accessing default semantic model

[Bhargava05]

I have a lakehouse that has multiple tables in different schemas, I want to share the Lakehouse with an user such that he has only access a particular schema, query the schema and build reports on data from that schema.

For this i have enabled one lake data access and then assigned a role to the user that has read access to that particular schema and also granted access to that schema using sql granular permissions.

Now i shared the lakehouse with just build semantic model with a user with only build reports based on the default semantic model permissions, such that user can query the data using sql endpoint and build reports, explore the data using semantic model.

But the user reported the below error; 

How do i solve this and i only give access to the user such that he can build reports on data from that schema.

Any help is appreciated, Thanks!

[nilendraFabric · Accepted solution]

Hi @Bhargava05 

If the user only has access to a specific schema or folder, but the default semantic model references tables or objects outside their permission scope, the model fails to load for them, resulting in the error.
• Even if you assign “Build” or “Read” permissions on the semantic model, the underlying data access is still enforced at the Lakehouse level

[Bhargava05 · Accepted solution]

Hi @nilendraFabric  thanks for your reply.

I have given access to underlying schema at the lakehouse level as well, using one lake data access. So in that case it shouldnt throw the error, and also let me know if have any suggestions for my case where i wanted to give user access to only specific schema and also he can build reports based on that schema.

I know one lake data access can be used for Lakehouse and sql granular permissions for sql endpoint but following both of those didn't  work.

[v-kathullac · Accepted solution]

Hi @Bhargava05 ,

we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?

If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.

Regards,

Chaithanya.

[Bhargava05 · Accepted solution]

@v-kathullac  it didnt get resolved yet, i have a sceanrio where end user should be able to access default semantic model and build reports based on it. Would be able to guide me through the steps/permissions i need to implement to achieve above.

[Bhargava05 · Accepted solution]

@v-kathullac  it didnt get resolved yet, i have a sceanrio where end user should be able to access default semantic model and build reports based on it. Would be able to guide me through the steps/permissions i need to implement to achieve above.

[v-kathullac · Accepted solution]

Hi @Bhargava05 ,

Below are the few points which can resolve your issue.

• Publish your semantic model (dataset) to a Power BI workspace.

• Ensure the dataset is modeled correctly with necessary measures and relationships.

• Add end users or user groups to the workspace with Viewer role.

• Grant Build permission on the dataset explicitly to those users/groups.

• Optionally, make the dataset discoverable in the Data Hub.

• Instruct users to open Power BI Desktop → Get Data → Power BI Datasets → select the shared dataset.

• Alternatively, users can go to Power BI Service → Data Hub and click Create Report on the dataset.

• Users will build reports using a live connection to the semantic model.

Regards,

Chaithanya.

[v-kathullac · Accepted solution]

Hi @Bhargava05 ,

we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?

If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.

Regards,

Chaithanya.

[nilendraFabric · Accepted solution]

Hi @Bhargava05 

If the user only has access to a specific schema or folder, but the default semantic model references tables or objects outside their permission scope, the model fails to load for them, resulting in the error.
• Even if you assign “Build” or “Read” permissions on the semantic model, the underlying data access is still enforced at the Lakehouse level

[Bhargava05 · Accepted solution]

Hi @nilendraFabric  thanks for your reply.

I have given access to underlying schema at the lakehouse level as well, using one lake data access. So in that case it shouldnt throw the error, and also let me know if have any suggestions for my case where i wanted to give user access to only specific schema and also he can build reports based on that schema.

I know one lake data access can be used for Lakehouse and sql granular permissions for sql endpoint but following both of those didn't  work.