Forum Discussion
Error returned: 'OLE DB or ODBC error: [Expression Error] The key didn't match any rows in the table
Anonymous
A typical case would be when you connect to an datasource and your Query attempts to access a table or column that does not exist in your datasource. Check if there is any table/column names are not matching.Reference:
Paul Zheng _ Community Support Team
If this post helps, please Accept it as the solution to help the other members find it more quickly.
Anonymous
A typical case would be when you connect to an datasource and your Query attempts to access a table or column that does not exist in your datasource. Check if there is any table/column names are not matching.
Reference:
Paul Zheng _ Community Support Team
If this post helps, please Accept it as the solution to help the other members find it more quickly.
I encountered a similar issue in my PowerBI reports where I discovered that the sample file had a sheet named 'data,' whereas the latest file had a sheet named 'DATA.' Later I changed the sheet's name from "DATA" to "Data" and I got my result.
I am getting the same message error: OLE DB or ODBC error: [Expression.Error] The key didn't match any rows in the table..
But I have data being sourced from hundreds of files, filtered out by file name and tab name parrameters. Is there any way I can figure out in which excact file an error might possibly be?did you ever figure this out or get an answer? i have the same issue. it tells me i have an error but not what or where it is.
In my case, I was pulling data from a folder containing multiple Excel files. The issue was that my query was looking for a 'table' within the Excel file called Table1, and in a couple of cases the Excel table had a different name. It would be helpful though if PBI at least told you which file it had failed on!
What is the best/fastest way to do this? I have hundreds of files in a folder I am combining in Power BI and this is like looking for a needle in a haystack...I have checked every file that has been updated since the last refresh, and I cannot find any discrepancies.
