Getting Error fetching data for the visuals where the protocol is "analysis-services"

Hi v-mizade, 

When a visual says it can’t connect to a data source with a {"protocol":"analysis-services" ...} connection, it’s telling you the visual is using a live connection to a shared semantic model (dataset) in another workspace. In your details, the server points to the workspace Cloud Supply and the database is the semantic model “SCHIE Footer Template.” If you don’t have the right permissions to that model-or if cross-workspace use or app permissions aren’t set up-the live connection fails and every dependent visual shows “Error fetching data for this visual.”

Troubleshooting steps:

1. Give the right people access to the semantic model.
   In the Cloud Supply workspace, open SCHIE Footer Template → More options → Manage permissions, and grant your users or, preferably, an Entra ID group, Read (and optionally Build) permission. Microsoft’s docs explain the difference between Read and Build here: Build permission for shared semantic models.
2. If you distribute via an App, include dataset permissions in the App.
   Update the App (audience settings) and enable “Allow users to build content with the semantic models in this app.” If the semantic model lives in a different workspace than the App, you still must grant permissions directly on that model: Publish an app in Power BI.
3. Ensure your tenant allows using models across workspaces.
   Ask a Power BI/Fabric admin to confirm the tenant setting “Use semantic models across workspaces” is enabled: Control the use of semantic models across workspaces.
4. Confirm licensing lines up with your capacity.
   Viewers need Pro/PPU unless the workspace is on Premium/Fabric capacity that allows free viewers. See: Feature availability for Free users.

Live-connected visuals query the semantic model via the Analysis Services (XMLA) endpoint. If the viewer lacks permission to that model, the connection is rejected and you see “Error fetching data for this visual.” Community threads with the same signature typically trace back to missing model access: example thread. Microsoft’s docs cover Read/Build here: Build permission for shared semantic models.

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.