This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
I have a report where I am trying to connect to someone else's semantic model. When I try, I get an error saying the specific PBI workspace is not found. However, when I try on a blank report, it works just fine. Is there anything that I can try to resolve this issue?
Solved! Go to Solution.
If you are connecting to a published semantic model in the service it's most likely permissions. Make sure that your user or your user is in a group that has "Read/Build" permissions on the semantic model published in the service.
If you are connecting to a published semantic model in the service it's most likely permissions. Make sure that your user or your user is in a group that has "Read/Build" permissions on the semantic model published in the service.
So this response confuses me because if I can connect to the semantic model on a blank new report, wouldn't that mean I have the correct permissions? I am not sure why I can't connect on the report where I need to connect to the model.
Upon further research, this looks like this might be the correct answer because apparently I can have a live connection if I have read access to the model but if I want a directquery connection I need build access.
I'm glad it worked for you!
Hi @kmei001 , are you trying to connect to the same semantic model on both files? If so, was this semantic model recently moved or renamed?
If so, I recommend trying to clear the cache to see if it will allow you to re-establish the connection on your file. To clear the cache:
File > Options and settings > Data source settings
Under Global Permissions, Clear Permissions for live connections to Power BI Service.
File > Options and settings > Options > Global
Under Data Load, click Clear cache.
If this helped, please mark it as the solution so others can benefit too. And if you found it useful, kudos are always appreciated.
Thanks,
Samson
Connect with me on LinkedIn
Check out my Blog
The model was not moved or renamed. I have done the steps you've suggested anyway and this did not make any change. Still getting the error.
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 30 | |
| 24 | |
| 23 | |
| 17 | |
| 16 |
| User | Count |
|---|---|
| 61 | |
| 35 | |
| 30 | |
| 23 | |
| 22 |