Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredGet Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
Hello folks,
Can you please help me with the issue below?
My table has fields from the two dim_tables shown below, and I'm not using any DAX measure.
I've searched what the error msg could be and how to fix it, and I found the article below, but I'm stuck because I'm not using any DAX measure here. What could that be?
https://blog.crossjoin.co.uk/2021/10/31/understanding-the-the-operation-was-cancelled-because-of-loc...
Many thanks,
R.
Solved! Go to Solution.
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.
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 ,
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 -
You can find may articles online regarding this error.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
Check out the October 2025 Power BI update to learn about new features.