Forum Discussion
Advocate IError viewing Paginated Report when Semantic Model exists in a different workspace
Over the weekend our users have encountered a new error when viewing a paginated report that connects to a semantic model from a different workspace, even though the users have read permissions on the semantic model.
- Workspace A contains Semantic Model
- Workspace B contains Paginated Report, that connects to Semantic Model from Workpace A
A short-term solution that has resolved this is to add the users as Viewers into Workspace A (when previously they only had direct read permissions on the Semantic Model, but no workspace access). This isn't ideal though, so I'm wondering if this has affected others and if this is a new bug?
Hi Richflan and pread,
This was an issue with a small change we made to improve connections for PBIDatasets. We turned off the change. You should be back working as before now or very soon.
7 Replies
bradsyMicrosoft Employee
Thank you for posting this. It indeed may be a bug. We are investigating, I will let you know once we understand what is going on.
- Idrissshatila
Super User
Hello ,
I don't know if this is also related to the issue that many people are facing with refresh on Power Bi service.
check
I opened an issue with microsoft support to investigate it, you can follow the issue in the link to know the latest update regarding this issue
https://community.fabric.microsoft.com/t5/Issues/The-OData-connector-failed-with-the-following-error-We-cannot/idi-p/4140532#M109217 We have experienced the same issue, it started on Friday. We found that it wasn't affecting any users who had "Build" permissions to the dataset, only those with "Read" only access. Adding the users to dataset workspace as viewer also fixed the problem, however this is again not ideal.
richflanGlad to hear I'm not going mad at least! Yeah, I'd noticed that granting build permissions resolved the issue but like you said this is actually even less ideal for us 😅
- bradsy
Hi Richflan and pread,
This was an issue with a small change we made to improve connections for PBIDatasets. We turned off the change. You should be back working as before now or very soon.
