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

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Frequent Visitor

Semantic Model Dataset fail to refresh due to "Key did not match any rows in the table"

Hi guys, 

Just some background , i have some data that was pulled in from snowflake. The snowflake datasets sits in dataflow with a schedule refresh every 4 hours. I then created a PBI desktop to connect directly to that data flow (Refresh works fine on PBI desktop). However, the issues come after uploading it into service. I constantly get an error :



Data source error: [ValidateMarkupTags][ccon]Expression.Error: The key didn't match any rows in the table.. Key = [ccon][workspaceId = "6b30afcc-43ab-4eea-a79##########"][/ccon]. Table = [ccon]#table({"workspaceId", "workspaceName", "workspaceType", "Tags"}, {})[/ccon]. [/ccon];[ccon]The key didn't match any rows in the table.[/ccon]. The exception was raised by the IDbCommand interface. Table: f_learning_course_user_new.


Some of the things that i've tried are
- Deleting that dataset and republishing

- Checking my workspace id, so far it matches.

Lineage View


Hope someone is able to advise on this. thank you.


Community Support
Community Support

Hi @Jared__ 


The error message you're encountering suggests there's a mismatch with the keys in one of your tables after publishing to the service. Here are the steps you can take to troubleshoot and resolve the issue:


Ensure that the dataset refreshes without any issues in Power BI Desktop.


Double-check the relationships and keys within your tables to ensure they match your data model expectations.


Confirm that the Workspace ID in your data source settings matches the ID of the workspace where the dataflow is located.


Verify that the dataflow itself is successfully refreshing and does not have any errors.


Utilize the Lineage View feature in Power BI Service to examine the dataflow and dataset dependencies.


Look for any discrepancies or broken connections that might indicate where the key mismatch is occurring.


Navigate to the dataset settings in Power BI Service.


Update the credentials and connection details to ensure they are current and accurate.


Attempt a manual refresh of the dataset in Power BI Service.


If it fails, carefully review the error message for additional clues about the mismatch.


Check if there have been any schema changes in the Snowflake data source that might affect the dataset.


Look for column changes, especially those involved in key relationships or transformations.


After making any necessary corrections in Power BI Desktop, republish the dataset to Power BI Service.


If using an incremental refresh policy, verify that the configuration is correct and that the keys used are consistent with the data source.



Nono Chen

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Community Champion
Community Champion

Hi @Jared__ 

Datasets on top of Dataflows need to be refreshed after the refresh of Dataflows had finished otherwise it could create the mismatch


Amine Jerbi

If I answered your question, please mark this thread as accepted
and you can follow me on
My Website, LinkedIn and Facebook

Helpful resources

Europe Fabric Conference

Europe’s largest Microsoft Fabric Community Conference

Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.

July 2024 Power BI Update

Power BI Monthly Update - July 2024

Check out the July 2024 Power BI update to learn about new features.

July Newsletter

Fabric Community Update - July 2024

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