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

[John_DeKock]

Hi all, 

I created a report that uses an existing Power BI Dataset, published the report in a App and shared it with the entire organization.

Some people can see the report, some people cant.....

Here's the error the users who CANT see the data and the visual:

Error fetching data for this visual

A connection could not be made to the data source with the Name of '{"protocol":"analysis-services","address":{"server":"powerbi://api.powerbi.com/v1.0/myorg/BASE%20Platform","database":"Boliden Power BI Monitoring Report"},"authentication":null,"query":null}'.

Please try again later or contact support. If you contact support, please provide these details.

See details

Activity ID: fbd8fb4b-bc7c-47f6-8a5d-6e16cbdd8d49
Request ID: 46f11a92-0c4e-444b-b7b6-8c91e7227f64
Correlation ID: 62736acc-4207-96b5-af6f-c7cc14b4079a
Time: Wed Apr 23 2025 09:56:50 GMT+0200 (Central European Summer Time)
Service version: 13.0.25729.37
Client version: 2504.2.23752-train
Cluster URI: https://wabi-north-europe-i-primary-redirect.analysis.windows.net/

I have tried playing around with the access to the underlying semantic model.......but it doesnt make sense because some people can see it, some people cant....

We are currently on a F64 capacity if that counts for anything...

[v-kpoloju-msft · Accepted solution]

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.

[v-kpoloju-msft]

Hi @John_DeKock,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-kpoloju-msft]

Hi @John_DeKock,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.

[v-kpoloju-msft]

Hi @John_DeKock,

I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.
Thank you.

[CSF]

I tried to severely reduce the amount of data that my report is loading, to follow a suggestion by @Cookistador . That did not change anything.

Here's the export from performance analyzer. Would you be so kind as to review, @Cookistador ?

[Cookistador]

For a test purpose 

Can you delete the card (New)? If it improves your performance 

Can you extend this step to check what is taking so long ?

[CSF]

It took a lot less time on this refresh...

...does it indicate anything to you, @Cookistador ? Thank you so much.

I'd paste the DAX Query here but for infosec concerns.

[Cookistador]

the meaning is you have to improve your dax query

Maybe your visual is returning to much line or just the dax code is pretty heavy

Generally this is the two reason of this error message

Maybe, you could anonymize your dax query, just to see if it is a complicated one or if the issue is comming from the amount of data retrieve

[CSF]

Thanks for your consideration but I don't think this is about the amount of data returned by the DAX query. The report works fine for members of my workspace. If the volume of data was my problem, I would expect everyone to get an error message. I would also expect a completely different error message.

[CSF]

My solution was to share all of the semantic models that were connected by DirectQuery with the intended end users.

[CSF]

same date, same problem. I can't find any solution yet though I am curious about what Cookistador suggested.

My report works fine for members of my (premium) workspace but fails for other people in the organization with the same error message... A connection could not be made to the data source with the Name of '{"protocol":"analysis-services","address":{"server":"powerbi://api.powerbi.com/v1.0/myorg/____________","database":"____________"},"authentication":null,"query":null}'.

[ribisht17]

hi @John_DeKock 

Please check this post Error fetching data for this visual - Microsoft Fabric Community

Regards,

Ritesh

Community Champion

Please mark the answer if helpful so that it can help others

Dance-Sing with Data Projects - YouTube

[Cookistador]

Just to test

Can you apply a slicer to return 20 lines in your table?

It looks like that it show to much data

You can also use performance analyzer to have a look on it

And share us the results 🙂