Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Power BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.

Reply
rdnguyen
Helper V
Helper V

Dataflow table lost

Hi there, 

 

I recently experienced the case where Tables within dataflows suddenly become not recognizable. When I go and edit the dataflow, the table was there, but no other dataflow which refer to that staging one able to see it.

 

Note: Deployment pipleline is in use and I sync the version from Test to Production again, but nothing works.

 

This dataflow series has been running smoothly for a month and no new update apply to it so far. Failure came in all at a sudden.

 

Error message as below:

Error: Expression.Error: The key didn't match any rows in the table. Key = [entity = "AR_L3YTD"] Table = #table({"entity" "dataCategory" "Data" "Tags" "ItemKind" "ItemName" "IsLeaf"} {}). RootActivityId = 57fae13f-1c90-4710-ab80-75f1c4afd98d.Param1 = Expression.Error: The key didn't match any rows in the table. Key = [entity = "AR_L3YTD"] Table = #table({"entity" "dataCategory" "Data" "Tags" "ItemKind" "ItemName" "IsLeaf"} {}) Request ID: cc758588-4156-4f03-840c-fd13879a6483.

1 ACCEPTED SOLUTION
v-cazheng-msft
Community Support
Community Support

Hi @rdnguyen,

 

Just as the error message “The key didn’t match any rows in the table” said, this issue should be caused by there is a table name that can't be found now. And normally, these points could be the reason why this error may happen.

  • The table name has been changed, for example in the data source itself.
  • The account used to access the table doesn't have sufficient privileges to read the table.
  • There may be multiple credentials for a single data source, which isn't supported in Power BI Service. This error may happen, for example, when the data source is a cloud data source and multiple accounts are being used to access the data source at the same time with different credentials. If the data source is on-premises, you'll need to use the on-premises data gateway.

For more details, you could refer to Error: The key didn't match any rows in the table.

 

To remove this error, you need open the Power Query Editor of your dataflows and navigate to the affected query, if you don’t see the exact error, click on Refresh Preview and the same error will be visible there:

vcazhengmsft_0-1659495617715.png

 

Check M script in Advance Editor, if you see the table mentioned in error message is hardcode there, that's why it will fail if the name changed or the table dropped for any reason. You can fix that in the Advanced Editor by changing the name to the new name or you can do it by clicking on "Edit Settings" button in the alert message. And click on the new table name or the target table in the prompted dialog. 

 

If there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly. If I misunderstand your needs or you still have problems on it, please let me know. Thanks a lot!

 

Best Regards,                                               

Community Support Team _ Caiyun

View solution in original post

1 REPLY 1
v-cazheng-msft
Community Support
Community Support

Hi @rdnguyen,

 

Just as the error message “The key didn’t match any rows in the table” said, this issue should be caused by there is a table name that can't be found now. And normally, these points could be the reason why this error may happen.

  • The table name has been changed, for example in the data source itself.
  • The account used to access the table doesn't have sufficient privileges to read the table.
  • There may be multiple credentials for a single data source, which isn't supported in Power BI Service. This error may happen, for example, when the data source is a cloud data source and multiple accounts are being used to access the data source at the same time with different credentials. If the data source is on-premises, you'll need to use the on-premises data gateway.

For more details, you could refer to Error: The key didn't match any rows in the table.

 

To remove this error, you need open the Power Query Editor of your dataflows and navigate to the affected query, if you don’t see the exact error, click on Refresh Preview and the same error will be visible there:

vcazhengmsft_0-1659495617715.png

 

Check M script in Advance Editor, if you see the table mentioned in error message is hardcode there, that's why it will fail if the name changed or the table dropped for any reason. You can fix that in the Advanced Editor by changing the name to the new name or you can do it by clicking on "Edit Settings" button in the alert message. And click on the new table name or the target table in the prompted dialog. 

 

If there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly. If I misunderstand your needs or you still have problems on it, please let me know. Thanks a lot!

 

Best Regards,                                               

Community Support Team _ Caiyun

Helpful resources

Announcements
June 2025 Power BI Update Carousel

Power BI Monthly Update - June 2025

Check out the June 2025 Power BI update to learn about new features.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.