Forum Discussion
Microsoft EmployeeSequence contains no matching element
Hi ,
All of a sudden dataset refresh from PowerBI started throwing error "Sequence contains no matching element", Same query in KUSTO running fine and in PowerBI desktop also till yesterday it was accepting change was refreshing.
I am blocked as i am not able to make any change in PowerBI Dataset not its refreshing but throwing e
Get as much info as you can and file a bug report or post in the Issues forum. On Wednesday, Feb 10, 2021, MS released a new updated Power BI Desktop that may contain this error. You may have received it automatically if your version is through the MS Store, or you manually downloaded and installed the update.
Include as much info as possible. Your PBI desktop version, the data source, model type (Import, DQ, Live Connection), etc. Assume the support person knows nothing about your setup - because they don't. The more info the better. 😉
8 Replies
- edhans
Community Champion
Get as much info as you can and file a bug report or post in the Issues forum. On Wednesday, Feb 10, 2021, MS released a new updated Power BI Desktop that may contain this error. You may have received it automatically if your version is through the MS Store, or you manually downloaded and installed the update.
Include as much info as possible. Your PBI desktop version, the data source, model type (Import, DQ, Live Connection), etc. Assume the support person knows nothing about your setup - because they don't. The more info the better. 😉
AshishRanjan
- edhans
Thanks. I marked my post as a solution so this thread would be seen as closed. MS does check the Issues forum, so they hopefully see it in time to fix.
AlexaderMillandHelper III
Did you ever find a way around this? Suddenly one of my reports does the same when trying to refresh all the tables at once. When refreshing just 1 table at a time it works fine.
- edhans
AlexaderMilland - can you please submit a support ticket at Support | Microsoft Power BI for this? MS will need to collect some diags to see why this issue seems to have crept back up.
- edhans
this was fixed months ago AlexaderMilland but yours is now the 2nd person I've seen in as many days where it has cropped back up....
- AlexaderMilland
FYI it just happened again. Same report though 😕
- technolog
Super User
In my case, I just found one of the freshly added measures via Tabular Editor that was breaking the update. Removed it from the report. Added it again with a different name and everything worked.
Finding that measure was a matter of successively deleting measures until the update worked.
Also from the recommendations I've seen:
Check for Duplicate Elements: Ensure that the data or elements you are querying do not contain duplicates when they are not supposed to. This is often the case when you expect a unique identifier but find multiple entries with the same identifier.
