Forum Discussion
Several datasets in one workspace - API refresh failures
Hi, anvais
I assume this error could be an issue with your M script within your Power BI Desktop file. It can also be due to an out-of-date Power BI Desktop version. You may check the data format between Azure SQL and Query Editor in Power BI Desktop and set up data format for every column.
For further information, you may refer the following links.
Expression.Error: The key didn't match any rows in the table
Troubleshooting refresh scenarios
Best Regards
Allan
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi, and thanks for your reply. I'll look into it, but everything suggested shouldn't be the issue in our case. Feels like we've taken care of it already.
For me the randomness is confusing - the table the error emerges from differs basically every night and the datasets that fail are always a set of five out of ten but the fails are random within that group. It's exactly the same power bi file that we upload to service and for each user group we only change the SQL source credentials so it loads different schema into the model. The schema is always in the same exact format for each power bi file, only the content varies. The data types are always forced to follow the same structure as everything is stored in our DW. Also, the refresh completes without any errors in the morning through the API or the UI - unless I start 3-5 refreshes simultaneously.
That's why I'm thinking it has to be with some kind of limited amount of parallel refreshes one can run in Service. But I can't find any documentation related to this topic. Also, when we initiate the refresh we always insert the credentials and one parameter into the model - can this be something the service isn't able to handle when multiple (2-10) refreshes are running at the same time?
Best,
anvais
