Refresh Error - "The key didn't match any rows in the table"

[Bhartman30]

We received this error starting around 2:30 pm ET today when the datasets refreshed in the service: "The key didn't match any rows in the table".

The datasets refresh successfully in the desktop but not in the service. This may be a coincidence, but it also was the same time I added my first Dataflow. 

[Anonymous]

I found something that may help.  In my case, removing the option to "include in report refresh" from all tables in the model file resolved the issue. Instead of refreshing the model separately, the tables will be refreshed in the model once the dataflow is refreshed and the error stopped. 

[HSHH]

Same issue here - we have other dataflows that are configured in exactly the same way that work absolutely fine. But one dataflow created last week shows the same behaviour as described above.

[v-juanli-msft]

Hi @Bhartman30

it also was the same time I added my first Dataflow

what is your dataflow?

The error message told that the key didn't match any rows in the table,I afraid that there is something wrong in your flow's configuration.

Please check your flow to see if you have some configuration wrong in the flow

Additionally, there is a similar thread disscussing about this issue and many users get their issues sloved with the help of it.

Please read and  check for your scenario.

https://community.powerbi.com/t5/Integrations-with-Files-and/Expression-Error-The-key-did-not-match-...

If you have any question, please don't hesitate to ask me.

Best Regards

maggie

[Anonymous]

Hi @v-juanli-msft The issue is a bit different from the thread you suggested. The problem in that thread was happening in PBI Desktop while the problem from @Bhartman30 is happening in PBI service.

I have been facing the same problem when using dataflows as a source for the models. The models refresh perfectly in PBI desktop but when in PBI service they give the "The key didn't match any rows in the table".

So far, the only way I found to fix it was to recreate the dataflow and change all sources from my datamodel. It is very labour intensive and still does not show me what was causing the issue.