Forum Discussion
Advocate IProcessing error: The key didn't match any rows in the table
I found a solution for my issue:
I had to recreate a new dataflow, with the same tables so that was easyAfter that, refresh the sources in PowerQuerry in my pbix file for each tables
And finaly, upload the pbix in Power Service, so that the dataset can switch on the new dataflow
Hope it can help you too
Hi DonHoog ,
We have reported your issue and have submitted to internal icm 320764522 , engineers are doing their best to fix this issue . please be patient and I will give you feedback here once there is any progress.
Best Regards,
Community Support Team _ Caitlyn
Advocate II have an update regarding this issue.
I have found out that you should not configure a gateway connection in your Dataset when using a Dataflow. We use a gateway on a particular server, then send the data to a Dataflow. Then in the Power BI desktop I call the data from the dataflow and publish it to Power BI service.
In the Settings of the Dataset you should under "Gateway Connection" > "Use an On-premises or VNet data gateway" > Set it to "Off". Then under Data Source Credentials you should click "Edit Credentials" and set your updated credentials. This solved the issue for me for a moment.
However, 2 hours later I refreshed the dataset and I got the same "The key didn't match any rows in the table" error. Do you have any idea why my error was solved temporarily and why it has now returned? When I execute the steps again I cannot fix the error anymore, it keeps displaying the red triangle. 😞