Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredGet Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
Hi,
we've got a solution that takes the data from various sources in one semantic model.
For some users, when they try to open the report they got error like this.
They got access to underlying semantic model.
Solved! Go to Solution.
If the user already has Build permission and is included in RLS, the issue may be due to cross-workspace access, chained dataset permissions, or a token/authentication glitch. Make sure the user has access to all upstream datasets, not just the immediate one. Also, try reopening the report in Power BI Desktop with a fresh sign-in. If datasets are spread across workspaces, ensure proper access and that Premium capacity is used for composite models.
Hi @notsobad__,
We haven’t heard back from you in a while regarding your issue. let us know if your issue has been resolved or if you still require support.
Thank you.
Hi @notsobad__,
Checking in to see if your issue has been resolved. let us know if you still need any assistance.
Thank you.
Hi @notsobad__,
Have you had a chance to review the solution we shared by @BhavinVyas3003 ? If the issue persists, feel free to reply so we can help further.
Thank you.
This error usually comes when a user opens a Power BI report that pulls data from another semantic model but doesn’t have the required Build permission on that dataset. Even if they can view the dataset, Build access is needed for such connected models (like DirectQuery or composite models). To solve it, go to the dataset’s workspace, click on Manage Permissions, and give Build access to the affected users. Also, make sure the user has access to both the report and dataset workspaces, and check if any RLS or login issue is blocking access.
The user has access to datasets with build permission and is included in RLS.
If the user already has Build permission and is included in RLS, the issue may be due to cross-workspace access, chained dataset permissions, or a token/authentication glitch. Make sure the user has access to all upstream datasets, not just the immediate one. Also, try reopening the report in Power BI Desktop with a fresh sign-in. If datasets are spread across workspaces, ensure proper access and that Premium capacity is used for composite models.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
Check out the October 2025 Power BI update to learn about new features.
| User | Count |
|---|---|
| 54 | |
| 18 | |
| 11 | |
| 10 | |
| 9 |