Forum Discussion
Build permission on semantic model does not allow user to use semantic model in Power BI desktop
- 1 year ago
Hi KimTutein
If the user has the correct permissions but still cannot see the dataset in Power BI Desktop or Data Hub, try the following steps:
Ask the user to clear their Power BI Desktop cache:
- Go to File > Options and Settings > Options > Diagnostics > Clear Cache.
Ensure the dataset isn't hidden from the Data Hub:
- In the Power BI Service, go to the dataset settings and check that Featured in Apps or Certify/Promote options are enabled for better visibility.
Confirm that your Power BI admin tenant settings allow external connections like Analyze in Excel and viewing datasets.
Create a test user with identical permissions to replicate the issue. If it persists, there might be a bug.
Revoke and reapply Viewer and Build permissions to refresh the user's access.
- If none of these work, it could be a backend issue—reach out to Microsoft Support for further assistance.
Did I answer your question? Mark my post as a solution, this will help others!
If my response(s) assisted you in any way, don't forget to drop me a "Kudos" 🙂
Kind Regards,
Poojara
Data Analyst | MSBI Developer | Power BI Consultant
Please Subscribe my YouTube for Beginners/Advance Concepts: https://youtube.com/@biconcepts?si=04iw9SYI2HN80HKS
Hi Poojara_D12
Just a follow up for you and potential others in the community reading this post.
For now I am not able to get a test user due to internal company policies which makes it very difficult for me to test security. However I reproduced the problem yet another time and made a ticket to support. They have been able to reproduce the same behavior (not being able to see semantic model if you do not have contributor permission on the workspace). They have told me that this is how the product works. I have voiced me concern that we then really have not core way of giving just read access to a semantic model which is worring for me. As I see it the only way to give pure read is to make a workspace with a lakehouse reference a “core” lakehouse via. shortcuts (I would think that giving contributor right to a lakehouse would mean granting write to that lakehouse as well – I have not checked up on this but a concern of mine)
Regards
Kim