Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
Everything was working fine till yesterday and now I am getting the below error:
I checked sheet names and all and everything is fine. Anyone has a clue?
Thanks in advance!
Solved! Go to Solution.
@Anonymous this could be possible due to change in the column header in applied steps. To check the error, please go the first applied steps then go ahead one by one to check at which point you are geting the error. Then you will be able to identify the column which causing the error. I believe in your data, you are directly connecting to the DB so do not have control over the name of the columns.
Proud to be a Super User!
@Anonymous this could be possible due to change in the column header in applied steps. To check the error, please go the first applied steps then go ahead one by one to check at which point you are geting the error. Then you will be able to identify the column which causing the error. I believe in your data, you are directly connecting to the DB so do not have control over the name of the columns.
Proud to be a Super User!
I was not able to figure out which step created the problem and what chnaged in the data souce(other team members just play with the source). Finally, I deleted and imported athe source again.
@Anonymous Yes it happens many times with direct data sources. I hope your problem is resolved now. Thanks
Proud to be a Super User!
@Anonymous , Refer if these old solutions can match
https://systemmanagement.ro/2018/05/18/power-bi-the-key-didnt-match-any-rows-in-the-table/
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the October 2025 Power BI update to learn about new features.