Forum Discussion
Unable to Load Model error message
Hi, zz99b0
In fact, my previous answer focused on the issue of permissions, and I also reminded you to check the permissions of the workspace and datasets. But it seems that you didn’t care about this, and we ended up going in another direction. But I'm glad it was resolved in the end.
Generally speaking, if it is a simple report sharing, the permissions of the dataset are set by yourself when sharing, but if the user is granted access to the workspace, the permissions of the dataset will be automatically defined according to the access of the workspace.
If you don’t want users to modify or create your reports, you can change user access to 'viewer'.Different datset permission:
Workspace role capability:
Reference: Roles in the new workspaces
Best Regards
Janey Guo
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I am running into the same issue, but searching for a solution that doesnt require giving Member level access to the workspace.
The users I am sharing my report with all have the same licens and permission settings - that is, no direct access or shared permissions with any of the reports, data sets or workspaces.
As an administrator, I am granting view only access to the report through a direct share link.
Each user has a Pro Power BI licens, and yet for some reason some of them can load the report and others cant. All end users are internal and belong to my organization. The underlying data for the report is held in sharepoint, then moved to a dataflow.
I have asked each user to log out/log in, clear their browser data, make sure they are loading in chrome. I still have two users getting a "Unable to load the model" error.
Hi ncraft
I suggest you open a new post in the service forum, and then describe your problem clearly in order to get better help.
Best Regards
Janey Guo
I cannot believe I'm reading through this again and no straight answer to what seems to be a basic issue. The settings are muddled and confused as is the documentation and as per usual this is just a long list of people with the same issue and no clear answer to what's causing the issue. Well done Microsoft again. Not like this platform is ridiculously expensive or anything