How to resolve Power BI error - the key didn't match any rows in the table

[IPolonio]

Hello, i had problem when using Fabric , from Onelake , i was consuming a group of tables but , everything works on desktop , but the problem comes on the service. that throws me the error.

Data source error: Expression.Error: The key didn't match any rows in the table.. Microsoft.Data.Mashup.ErrorCode = 10061. Key = [Schema = "development", Item = "Reasoning"]. 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. Cluster URI: WABI-US-EAST-A-PRIMARY-redirect.analysis.windows.net Activity ID: 4af1359b-36a2-c4b1-cb95-42d37b982430 Request ID: 93d9a4cf-490e-0107-f41a-615e62bfdcc6 Time: 2025-12-01 16:09:04Z i created a new semantic model with any changes and threw me the same error

Here is the solution: on the service when you configure your cloud connection , be sure that you add the same user that you created the connection to the Onelake security in fabric , if not this will generate the so mentionated error

[v-veshwara-msft · Accepted solution]

Hi @IPolonio ,

Thanks for posting in the Microsoft Fabric Community and for sharing the solution.

This error might occur due to various reasons, and your point about aligning the cloud connection identity with the OneLake item permissions will be helpful for others facing similar behaviour.

Also, thanks to @lbendlin for sharing the blog link, which explains clearly why this error can occur and the related patterns.

Thank you for contributing to the community, and please reach out if you need any further assistance.

[lbendlin]

Chris Webb's BI Blog: Understanding The “The key didn’t match any rows in the table” Error In Power ...