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.
Hi, zz99b0
You can try to turn on this feature, because you have both local data and cloud data. Query is generally mixed query. Even the data in the cloud will pass through the gateway.
Because you are using a web connector, you need a gateway even if the data is on onedrive.
Unless you are importing files directly in the service.
Like this:
You can also try to connect in anonymous mode in the web connector to see if it solves the problem.
The error message is not clear, we can only eliminate the problems one by one.
Best Regards
Janey Guo
I think I have it finally solved. Here is what I did:
- Created a new workspace
- Granted users access to the workspace. I had not done that previously. I only wanted users granted access to specific reports, as I knew my workspace would grow in the future and I need to be able to segregate users.
- Deleted my gateway altogether.
So at this juncture:
- Users are granted access to the entire workspace as a Member
- Users are granted read access to my OneDrive folder via "Links giving access"
I really wanted more constrained access as I do not want users creating their own reports at this point, as the data model is not bullet-proof. As you really must have a complete understanding of the data model. But it gets me past my existing issue.
Not sure this is the right answer, but at least I'm totally dead in the water.
Jennifer
Thanks again for all your assistance. I apologize if you felt I was ignoring your recommendations, it certainly was not my intention, as I have alot vested in making this work given the visibility.
I'm am still new and thought I was following what you suggested. I had checked permissions on the report, data sources, gateway, and OneDrive. And to be totally honest, workspace itself didn't connect in my brain, since I had granted access to the report itself.
I do appreciate all your help.
Jennifer
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.