Error fetching data for this visual - A connection could not be made to the data source with the...

Hi John_DeKock,

Thank you for reaching out to the Microsoft fabric community forum. Thank you CSF, Cookistador, ribisht17, for your inputs on this thread. After reviewing the details you provided, I have identified few workarounds that may help resolve the issue. Please follow these steps:

Users do not have direct permissions on the underlying dataset (semantic model), even if they have access to the App and the Report. Power BI Apps and Reports inherit permissions to view the dataset only if the user has access to the dataset itself.

If a user does not have access to the semantic model (dataset), the live connection fails, and they see the connection error. This is why some users can see it (they already have permissions), while others cannot. Note: Being on F64 capacity is good (big enough for scaling and performance), but this issue is purely about permissions, not capacity or load.

Grant Direct Dataset Permissions: In Power BI, users need explicit permissions to access the dataset when reports connect via a live connection. Please go to the workspace where the dataset (Boliden Power BI Monitoring Report) is located. Select the dataset, click on Manage permissions, and add the missing users (or preferably, a security group) with at least Read access.
Manage semantic model access permissions - Microsoft Learn

Review App Permissions: When distributing reports through a Power BI App, ensure that the App settings grant users access to both the reports and the associated semantic models. While editing the App, check the Permissions section and confirm that the relevant options (e.g., Allow users to build content with the semantic models in this app) are correctly configured.
Publish and configure apps in Power BI - Microsoft Learn

Check for Row-Level Security (RLS): If Row-Level Security is enabled on your dataset, users must be assigned to the appropriate RLS roles. Otherwise, they will not be able to view any data, even if they have dataset access. Review the RLS settings by selecting the dataset and managing the Security roles.
Row-level security (RLS) with Power BI - Microsoft Learn

Additionally, review workspace roles to ensure users have suitable workspace permissions, but the primary cause here appears to be direct dataset access.

If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.

Thank you for using Microsoft Community Forum.