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, i have the same probleme since this week-end.
I'm in the same data pipeline configuration: I have my data in a PG-sql, then send the data to a Dataflow and in Power BI desktop I call the data from the dataflow and finaly, publish it to Power BI service.
i have the same error "The key didn't match any rows in the table"
But it seems that the probleme come for the dataflow, when i look at the credential settings, i have a dplication of my SQL database, but i cannont delete it.
And when i want to update the one in error, it refresh witthout ant validation/confirmation
I found a solution for my issue:
I had to recreate a new dataflow, with the same tables so that was easy
After 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
DonHoogI have also come to a solution, although I dont understand why exactly.
In the post below I explain that I updated the credentials.
Apparently that worked because I have no errors anymore for 2 days in a row now.
I guess I needed to wait for some time before the Power BI service understood the changes.
I am glad it is now fixed for us both but maybe the Power BI service people can try to minimize these bugs in the future. 😉