Dataflow Gen1 table not visible in Power BI despite successful refresh. "Key didn't match any row."

[barwe]

Hi everyone,

I'm experiencing an issue with a Dataflow Gen1 where one of the tables is not visible in Excel or Power BI Desktop using "Get Data → Power Platform → Power BI Dataflows", even though:

The table is correctly configured:

• It refreshes successfully as part of the dataflow execution.
• Enable Load is turned ON in the Power Query editor.
• The last transformation step returns data (non-empty).
• Other tables in the same Dataflow appear and work normally.

Troubleshooting already done:

• I verified the loadEnabled: true property in the exported MyDataflow.json file of the Dataflow.
• I checked that the table doesn’t appear in either:
  • Excel → Get Data → Power BI Dataflows
  • Power BI Desktop → Get Data → Power BI Dataflows
• I tried refreshing the dataflow again – refresh completes, but the table is still not visible.
• All other tables in the dataflow are accessible and working fine.

Refresh Error Message:

Expression.Error: The key didn't match any rows in the table.. Microsoft.Data.Mashup.ErrorCode = 10061. Key = [entity = "MyTable", version = ""]. Table = #table({"entity", "dataCategory", "Data", "Tags", "entityName", "version", "ItemKind", "ItemName", "IsLeaf"}, {}). ;The key didn't match any rows in the table.. The exception was raised by the IDbCommand interface. Table: MyTable.

Has anyone experienced similar behavior with Dataflows?

[CodingCam · Accepted solution]

If a Dataflow Gen1 table isn't showing up in Power BI even though it refreshes successfully, and you're seeing a "Key didn't match any rows in the table" error, it's likely due to a metadata or naming issue. You've already ensured Enable Load is turned on, and the entity type is correctly set to "Table" in the JSON. Try clearing your Power BI Desktop cache and re-authenticating your data flow connection. If that doesn't work, recreate or clone the data flow to reset any hidden metadata issues. Testing with just the problematic table first can help isolate the problem.

[v-kpoloju-msft · Accepted solution]

Hi @barwe,

Thanks for sharing the detailed troubleshooting steps you have already covered a lot. Also thanks to @CodingCam, @speedramps, for those inputs on this thread. 

Based on the error message: Expression.Error: The key did not match any rows in the table… Key = [entity = "MyTable", version = ""].

this typically points to an entity metadata issue or cache mismatch in the Power BI service or client tools.

Sometimes recent changes in a Dataflow (like adding/renaming a table) do not reflect properly due to cached metadata.

• Go to File → Options and Settings → Options → Data Load.
• Under Data Cache Management Options, click Clear Cache.
• Restart Power BI Desktop and try again.

Verify Final Step Returns a Table: Even with Enable Load = ON, Power BI will skip the table if the final query step returns a record/function instead of a table. Please check that the last step in your Dataflow query returns a proper table (e.g., a result of Table.Transform... and not Record.Field...).

The empty version string may indicate the table was recently renamed or added and metadata has not synced correctly. Try renaming the table slightly (e.g., MyTable → MyTable_New), save and refresh the Dataflow. Then try accessing again from Power BI Desktop or Excel.

Gen1 Dataflows sometimes do not  expose new or modified entities properly. As a workaround:

• Export the Dataflow as .json, remove the affected entity, re-import with a new name
• Or consider moving to Dataflow Gen2, which offers better reliability and visibility.

A similar case was discussed here, which might also help:
Solved: Tables missing when connecting to dataflow from PB... - Microsoft Fabric Community

Hope this helps clarify things and let me know what you find after giving these steps a try happy to help you investigate this further.

Thank you for using the Microsoft Community Forum.

[v-kpoloju-msft]

Hi @barwe,

Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.

Thank you.

[v-kpoloju-msft]

Hi @barwe,

Hope you had a chance to try out the solution shared earlier. Let us know if anything needs further clarification or if there's an update from your side always here to help.

Thank you.

[v-kpoloju-msft]

Hi @barwe,

Just wanted to follow up one last time. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.

Thank you.

[CodingCam · Accepted solution]

If a Dataflow Gen1 table isn't showing up in Power BI even though it refreshes successfully, and you're seeing a "Key didn't match any rows in the table" error, it's likely due to a metadata or naming issue. You've already ensured Enable Load is turned on, and the entity type is correctly set to "Table" in the JSON. Try clearing your Power BI Desktop cache and re-authenticating your data flow connection. If that doesn't work, recreate or clone the data flow to reset any hidden metadata issues. Testing with just the problematic table first can help isolate the problem.

[speedramps]

Sorry I am not 100% sure this answer will help ....

Watch this video. It may help ..
https://www.youtube.com/watch?v=JZSdAvGAq_E

Click thumbs up because I have tried to help.

Then click accept solution if it works.

Thank you.