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