Forum Discussion
Power BI - Error Fetching data for this visual - Failed to execute DAX
- 4 months ago
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
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