"The key didn't match any rows in the table" with Gen2 Dataflow sources in semantic model

[DJF]

dear forum

I am encountering the error "The key didn't match any rows in the table." in my semantic models very randomly.

The entire error is:

{"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"<ccon>The key didn't match any rows in the table.</ccon>"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ErrorCode","detail":{"type":1,"value":"10061"}},{"code":"Microsoft.Data.Mashup.ValueError.Key","detail":{"type":1,"value":"[entity = \"Fact_SumTotal_Auslastungsreport\", version = \"\"]"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"Expression.Error"}},{"code":"Microsoft.Data.Mashup.ValueError.Table","detail":{"type":1,"value":"#table({\"entity\", \"dataCategory\", \"Data\", \"Tags\", \"entityName\", \"version\", \"ItemKind\", \"ItemName\", \"IsLeaf\"}, {})"}}],"exceptionCulprit":1}}}

I do get this error in different models, with different sources, at different times. Sometimes repeatedly, sometimes it is resolved with the next refresh of that model.

In most cases the source is a Dataflow Gen2. But all of the affected sources did not change in days/weeks/months. Their schema is stable and does not need changes. In most cases I do refresh data daily, in some the dataflows havn't been refreshed in weeks.

The issue thatgets closet to mine is: Solved: Refresh issue with Gen1 dataflows linked to Gen2 d... - Microsoft Fabric Community

But I did not have any success with the given solution.

Does anyone of you have any more hints on this problem?

thank you very much.

[v-echaithra]

Hi @DJF ,

May I ask if you have resolved this issue? Please let us know if you have any further issues, we are happy to help.

Thank you.

[v-echaithra]

Hi @DJF ,

We’d like to follow up regarding the recent concern. Kindly confirm whether the issue has been resolved, or if further assistance is still required. We are available to support you and are committed to helping you reach a resolution.

Thank you.

[v-echaithra · Accepted solution]

Hi @DJF ,

This error usually occurs when the semantic model tries to access a Dataflow Gen2 entity while its metadata is temporarily unavailable.

In Microsoft Fabric, Dataflow Gen2 outputs are written to storage and then registered in the metadata catalog before downstream items (like semantic models) can access them. Because this process is asynchronous, there can be a short window where the dataflow refresh has completed but the entity metadata is not yet visible. If the semantic model refresh runs during that time, Power Query may return an empty metadata response, resulting in the error "The key didn't match any rows in the table."
Since the refresh typically succeeds on the next attempt, this behavior is usually transient rather than a schema or configuration issue.
To reduce the chances of this occurring, consider ensuring the semantic model refresh runs after the Dataflow Gen2 refresh has fully completed, or introduce a short delay between the two refreshes, for example by orchestrating them through a Fabric Data Pipeline.

Best Regards,
Chaithra E.

[Juan-Power-bi]

Hi, this is a known intermittent issue with Dataflow Gen2 sources in semantic models, and the random/transient nature of it is actually the biggest clue — it's almost always a timing or availability issue on the Fabric backend side rather than anything wrong with your model or dataflow schema.
A few things worth checking:
1. Refresh orchestration — The most common cause is that the semantic model refresh kicks off before the Dataflow Gen2 has fully committed its data. Even if the dataflow shows as "succeeded", there can be a short window where the output isn't fully available. Try adding a delay between your dataflow refresh and your semantic model refresh, or better yet, use a Data Pipeline to chain them explicitly (Dataflow activity → wait → Semantic Model refresh activity). This is the most reliable fix.
2. The entity name in your error — the error references entity = "Fact_SumTotal_Auslastungsreport" specifically. Worth double-checking that the entity name in your semantic model connection exactly matches what's published in the dataflow, including casing. Gen2 can occasionally be sensitive to this after workspace migrations or capacity changes.
3. Capacity pressure — If your Fabric capacity is being throttled or is under heavy load at refresh time, Gen2 can return an empty metadata response, which is what triggers that "key didn't match any rows" error. Check your capacity metrics around the time of the failures to see if there's a correlation.
4. Re-bind the connection — If it keeps happening on specific tables, try removing and re-adding the Dataflow Gen2 connection in the semantic model. Sometimes the internal reference gets stale without the schema actually changing.
The fact that it resolves on the next refresh strongly points to option 1 — a pipeline with explicit sequencing is really the cleanest long-term solution for this.
Hope that helps! 🙂