Power BI - Error Fetching data for this visual - Failed to execute DAX

[KarenL7]

Hi

I have been creating a report which uses a one lake catalog model - which is working fine in Power BI Desktop.  I can publish this to the workspace and see the report without any issues.

However, when I let any users try to look at the report they can access the report, but not see any of the visuals.  The have this error message.  

I have seen similar issue but it was a while back - and was suggesting rebuilding the visuals -

https://community.fabric.microsoft.com/t5/Service/Error-fetching-data-for-this-visual/m-p/4643694

I shall try this, but  I was wondering if anyone had come across this at all?

Thanks

Karen

[v-pnaroju-msft]

Hi @KarenL7,

Thankyou for the update.

We kindly request you to share the feedback provided by the support team with the community, as it will help other members facing similar challenges and benefit the broader community.

[KarenL7]

Hi @v-pnaroju-msft 

Thanks 

Just to confirm - I did raise a support ticket in the end.  However, when I tried to share the issues, I was unable access the report either and had a permissions issue with the report and all the tables failed, including the dax - and I am an admin!

To resolve the issue I did the following -

- rebuilt the report totally from scratch

- looked at the lineage and changed permissions on the workspaces, and lakehouse - to ensure the user had read all, execute on sql endpoint on the original lakehouse.  

- They did not require any permissions on the event house which was upstream which is attached to the development version of the lakehouse

- I published the new report and they were able to see it.

It has taken a very long time and several reports, but I have got there.

Thanks to everyone for your help and patience, but permissions and a new report seems to have worked.  It has been very frustrating!

Karen

[v-pnaroju-msft]

Hi @KarenL7,

Based on our understanding, since users are able to access the semantic model, create DAX queries, and interact with slicers or dropdowns, but the visuals continue to fail, this behaviour likely points toward an upstream query execution or identity propagation issue during visual rendering. Visuals may execute live backend queries using the viewer's identity and may still validate access across upstream dependencies such as Eventhouse or other lineage items.

Kindly follow the validation steps mentioned below:
1.Review the complete lineage view to identify any remaining upstream dependencies.
2.Verify permissions not only on the semantic model, but also on all upstream objects such as Eventhouse or other entities involved in the lineage chain.

At this stage, we kindly request you to raise a Microsoft Support ticket and provide all relevant details for a deeper backend investigation using the link: Microsoft Fabric Support and Status | Microsoft Fabric

We hope the information provided above helps in resolving the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.

Thank you.

[KarenL7]

Hi @v-pnaroju-msft  I have raised a support ticket for this.

mainly as ai can see the eventhouse and dependencies now. 

I am unsure if this is the reason, as we do not want users to have access to these -Although it has been explained - why you have to give permissions to other areas which have nothing to do with the lakehouse concerned for a user to look at visuals?   Particuarly when the user can query the dataset and open the model -  so I have asked the question.

I will keep looking and testing permissions in the meantime, and if anything else works I will update.

Thank you all for your help, hopefully something will work!

Karen

[KarenL7]

 Hi @krishnakanth240  / @Shai_Karmani 

ok although this is  is still not working I have just checked the lineage of the dataset which was created from the lakehouse.  I note there is a vague reference in the model upstream a refrence from the lakehouse to an eventhouse which refers to different workspaces etc. None of these are in the dataset or directly in the lakehouse

which the user would not have access to at all.  But they can access the dataset, create dax and the model so I dont understand why they would need access just to see the visuals?  I rebuilt them and that did not work!

Therefore I am hoping that the eventhouse is not causing the issue.  User has permissions to that for reference but I am unable to give permissions to the other workspaces. If so I am not sure what to do!

@v-pnaroju-msft  are you able to help?  The solutions provided are great but I still needs some further assistance thank you! - or should I submit a support ticket?

I have tried the following

- created a new report removed visuals and added a new table uploaded it and it did not work

- I have changed all the permissions - even given access to the original workspace (which we did not want to do - but  this was done for a test) ensuring all permissions on the lakehouse, model and report.

- the user can access the dataset, create dax and even view the model.

- the user confirmed they refreshed visuals/ cleared cache before testing each time.

- there was a permissions error on the new report but was this was dealt and then the dax error came up.

- In power bi desktop the report works.

- The model is simple and no calculations.

- As admin I can see the report

We are now using Power BI Desktop March 2026 - any other ideas would be appreciated.  It is getting very frustrating.

Thanks

Karen

[v-pnaroju-msft]

Thankyou, @Shai_Karmani and @krishnakanth240  for your responses.

Hi @KarenL7,

We appreciate your inquiry through the Microsoft Fabric Community Forum.

We would like to inquire whether have you got the chance to check the solutions provided by @Shai_Karmani and @krishnakanth240to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.

Thank you.

[KarenL7]

Hi @krishnakanth240 / @Shai_Karmani 

I have been trying today - I have updated the permissions which has been suggested - including build

Also I have ensured that the user has had direct access to the original dataset - they can interact with this and see the model / table and even create dax if they should so wish.  So that is all working correctly as suggested.

However the error is still appearing on the report.  Except on 2 visuals - 2 drop down boxes - which the user can interact with.  Which is very odd.

As suggested in the other post - I know that I have rebuilt the visuals at one point and the issue persists.  Any other ideas are gratefully received.

Thank you for your help

Karen

[krishnakanth240 · Accepted solution]

Hi @KarenL7 

Since users can access the dataset but only slicers work while visuals fail which points to a data access or query execution issue rather than basic permissions. In OneLake or DirectLake scenarios, users also need proper read access to the underlying Lakehouse or Warehouse or SQL endpoint as visuals trigger actual data queries while slicers may rely on cached metadata. So ensure full data level access and validate identity propagation instead rebuild visuals

[KarenL7]

Hi @krishnakanth240 

Thank for coming back to me.

Just to confirm - "users also need proper read access to the underlying Lakehouse or Warehouse or SQL endpoint as visuals trigger actual data queries while slicers may rely on cached metadata."

I have given read permissions on the original lakehouse but not access to the original workspace (as we do not want this) - note we did this through an workspace app-

So we set up a copy of the lakehouse with full permissions, with access to that workspace - and they can now access the dataset as mentioned above

Unsure what else to change - I have also completely rebuilt the report from scratch as the 2 dropdown boxes were from the original datasets. 

From the help that I have - at least the user can explore the data and see the model that is a start.

I will keep looking into it! 

Thank you so much for your help

Karen

[KarenL7]

Hi @krishnakanth240 

Thank for coming back to me.

Just to confirm - "users also need proper read access to the underlying Lakehouse or Warehouse or SQL endpoint as visuals trigger actual data queries while slicers may rely on cached metadata."

I have given read permissions on the original lakehouse but not access to the original workspace (as we do not want this) - note we did this through an workspace app-

So we set up a copy of the lakehouse with full permissions, with access to that workspace - and they can now access the dataset as mentioned above

So what further do we need to change?

Thank you so much for your help

Karen

[krishnakanth240]

Hi @KarenL7 

Cause might be users don’t have permission on the semantic model or Lakehouse or Warehouse. Missing OneLake item access  that is SQL endpoint or delta tables. RLS or OLS blocking data. Dataset using DirectLake or DirectQuery without proper user access.

So workarounds are giving users access to workspace (viewer is not always enough), access to semantic model (build permission), access to underlying Lakehouse or Warehouse (read or SQL access). If using DirectLake then ensure users have read access to OneLake data

Also, you can ask affected user to open the dataset directly so if it fails then it is access issue

[KarenL7]

Hi @Shai_Karmani 

thanks for this, I will be testing this solution this morning - I have redeployed the report into a separate workspace to update the permissions to test.  I had the same error, but once I changed permissions and refreshed the visuals it went away.

However, I need to test this with several users to confirm that it is working for them.  To confirm which permissions they need.

I will accept as solution once confirmed.

Thank you for your help.

Karen 

[Shai_Karmani]

This usually comes down to permissions on the underlying semantic model rather than the report itself. A connected report only renders if the viewer has at least Read and Build on the source semantic model, plus Viewer access to the workspace that hosts the model. The "Failed to execute DAX" message is what users get when they can open the report but their identity is rejected when a visual tries to query the dataset.

Open the workspace that contains the semantic model, go to Manage access, and grant the affected users (or a security group) both Read and Build. If the model lives in a different workspace than the report, give them Viewer on that workspace too. Ask one of them to hard refresh and the visuals should populate without rebuilding anything.

If you also have RLS configured on the model, double check those users are mapped to a role, because an unmapped user on an RLS enabled model produces the same error.

If this helped, a thumbs up and accepting the solution would be appreciated.

Best,

Shai Karmani