Forum Discussion
Couldn't load data for this visual - no DAX.
- Anonymous4 years ago
Hi, Pragati11 It's a direct query. Not sure what happened, but I think it was because I was using some columns that I hid and were no longer available in the reporting view. I created a new table using only the available fields and it worked. Thanks.
Hi Anonymous ,
Are you importing this data live or via directquery in Power BI?
Locking conflicts error can happen whe bought data in above mode due to the parallel use of the tables say in your database and also in Power BI.
- Anonymous4 years agoNot applicable
Hi, Pragati11 It's a direct query. Not sure what happened, but I think it was because I was using some columns that I hid and were no longer available in the reporting view. I created a new table using only the available fields and it worked. Thanks.
- Pragati114 years ago
Super User
Hi Anonymous ,
Great that it is resolved for now. But I do think this can occur again as you are using a Directquery connection to access data from database.
Locking conflicts happen mostly from database end when bringing the data in directquery mode in Power BI. This could be due to various reasons -
- longer time in running the queries
- sometimes DAX queries can cause this as well - so better to make them better from performance point of view
You can find may articles online regarding this error.