March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
Hi,
I have the following issue. In the semantic model, the data source for one of the tables is another semantic model. When I open the report in Power BI Service, I can see the visuals connected with this table correctly. However, when another person opens the report, these visuals are not available and show the error: "Error fetching data for this visual."
The report is shared via an app, so users don’t have direct access to the workspace (where I do have access).
The table source, meaning the original report, is not included in the app.
What are the limitations in this scenario, and how can I work around them?
I assume that if app users also had workspace access, they would be able to see the visuals, correct? I don’t want to add users to the workspace, as I treat it as a development area. Would adding the table source report to the app resolve the issue? I'd prefer to avoid this, as the report is designed solely as a source for other reports. (Our company does not have a Fabric license and only uses Power BI Pro, so I can’t use other cloud tools for ETL purposes.)
Solved! Go to Solution.
Thank you lbendlin
Hi, @karolp
If your application relies on semantic models from other workspaces, ensure that all application users have access to the underlying semantic models. If the application or report is in the same workspace as the semantic model, make sure to include the reports associated with that semantic model in the application.
Publish an app in Power BI - Power BI | Microsoft Learn
Additionally, if the application contains reports using chained semantic models (also known as DirectQuery for Power BI semantic models and Analysis Services), ensure that you grant permissions to all semantic models in the chain when adding users to the audience group.
Publish an app in Power BI - Power BI | Microsoft Learn
If you do not want to give audiences in apps workspace roles, you can give them permissions to the semantic model alone:
Semantic model permissions - Power BI | Microsoft Learn
Manage semantic model access permissions - Power BI | Microsoft Learn
Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thank you lbendlin
Hi, @karolp
If your application relies on semantic models from other workspaces, ensure that all application users have access to the underlying semantic models. If the application or report is in the same workspace as the semantic model, make sure to include the reports associated with that semantic model in the application.
Publish an app in Power BI - Power BI | Microsoft Learn
Additionally, if the application contains reports using chained semantic models (also known as DirectQuery for Power BI semantic models and Analysis Services), ensure that you grant permissions to all semantic models in the chain when adding users to the audience group.
Publish an app in Power BI - Power BI | Microsoft Learn
If you do not want to give audiences in apps workspace roles, you can give them permissions to the semantic model alone:
Semantic model permissions - Power BI | Microsoft Learn
Manage semantic model access permissions - Power BI | Microsoft Learn
Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
thank you for the advice.
Granting permission to the underlying, chained semantic model resolved the issue. No further actions were needed.
Thank you again!
Make sure the users have "installed" both apps (by clicking each app link at least once).
There is one app connected to the workspace (I believe it’s not even possible to connect multiple apps to a single workspace, but that’s beside the point).
Both reports are in the same workspace, but only the report with the "Error fetching data for this visual" issue is added to the app. The second report is created solely to serve as an ETL and data source for other semantic models and reports within that workspace.
The problem only affects visuals connected to the table that uses the "ETL" semantic model as its data source. I have no issues viewing the correct content in these visuals from my account. However, other users only see the error message on those visuals. The difference is that I have access to the workspace, while they do not. I prefer to share the reports through the app rather than giving all users direct access to the workspace.
Is there a workaround for this?
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
User | Count |
---|---|
37 | |
22 | |
20 | |
10 | |
9 |
User | Count |
---|---|
59 | |
55 | |
22 | |
15 | |
12 |