Forum Discussion
Error fetching data for this visual Expression.Error: The key didn't match any rows in the table..
Posting a report to the web and I continually get this error:
Error fetching data for this visual
Expression.Error: The key didn't match any rows in the table.. Microsoft.Data.Mashup.ErrorCode = 10061. Key = [Schema = "dbo", Item = "ExactSalesOrderSyncs"]. Table = #table({"Name", "Data", "Schema", "Item", "Kind"}, {}). ;The key didn't match any rows in the table.. The exception was raised by the IDbCommand interface.
The report is using Azure database as the main source.
Any suggestions please?
Hi iancrocker,
Thank you for reaching out to the Microsoft fabric community forum. Thank you Akash_Varuna, alia12, for your inputs on this issue.After reviewing the details you provided, I have identified few workarounds that may help resolve the issue. Please follow these steps:
The error message "Expression.Error: The key didn't match any rows in the table" in Power BI's Power Query usually occurs when a query tries to access an element—such as a worksheet, table, or column that no longer exists or has been renamed in the data source.
Solved: I have this error: The key didn’t match any rows i... - Microsoft Fabric Community
Make sure that all worksheets, tables, and columns referenced in your query exist and retain their original names in the data source. When working with multiple files, maintain consistent sheet and table names across all files to avoid mismatches.
Update your Power Query steps to reflect any changes in the data source, including renamed or relocated elements. Instead of hardcoding sheet or table names, consider dynamically retrieving them to enhance the resilience of your queries.
In Power Query Editor, review each applied step to identify where the error occurs. This will help pinpoint the exact reference causing the issue.
Also kindly please go through the below solved solutions for better understanding:
Solved: Expression. Error: The key did not match any rows i... - Microsoft Fabric Community
Solved: how to resolve Power BI error - the key didn't mat... - Microsoft Fabric Community
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you for using Microsoft Community Forum.
6 Replies
Hi iancrocker Could you try referencing the table directly instead of using Source{[Schema=..., Item=...]}[Data]?
Use something like: ExactSalesOrderSyncs = Source[dbo].[ExactSalesOrderSyncs] or write a direct SQL query.
Had a similar issue before, turned out the table didn’t exist in the dataset when published, even though it worked in Power BI Desktop.
Make sure that the table is loaded in your model (not just referenced) and check for case sensitivity in schema/table names if you’re using an SQL query. Also, double-check that the credentials and privacy level settings for the Azure DB match what's inthe Power BI Service.
Hi iancrocker,
Thank you for reaching out to the Microsoft fabric community forum. Thank you Akash_Varuna, alia12, for your inputs on this issue.After reviewing the details you provided, I have identified few workarounds that may help resolve the issue. Please follow these steps:
The error message "Expression.Error: The key didn't match any rows in the table" in Power BI's Power Query usually occurs when a query tries to access an element—such as a worksheet, table, or column that no longer exists or has been renamed in the data source.
Solved: I have this error: The key didn’t match any rows i... - Microsoft Fabric Community
Make sure that all worksheets, tables, and columns referenced in your query exist and retain their original names in the data source. When working with multiple files, maintain consistent sheet and table names across all files to avoid mismatches.
Update your Power Query steps to reflect any changes in the data source, including renamed or relocated elements. Instead of hardcoding sheet or table names, consider dynamically retrieving them to enhance the resilience of your queries.
In Power Query Editor, review each applied step to identify where the error occurs. This will help pinpoint the exact reference causing the issue.
Also kindly please go through the below solved solutions for better understanding:
Solved: Expression. Error: The key did not match any rows i... - Microsoft Fabric Community
Solved: how to resolve Power BI error - the key didn't mat... - Microsoft Fabric Community
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you for using Microsoft Community Forum.Hi iancrocker,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hi iancrocker,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
