'Sequence contains no matching element' error

[Anonymous]

Hi,

I did some maintenance on my report which has only one datasource: Dynamics 365. The connection is through Dataverse. I loaded 6 tables and added a calculated date table myself, so it is not a complex model. The maintenance work in Power BI desktop was all fine, I could do my work in the query editor and refresh data over there, and nothing seemed off. However, after publishing it to the app, I got some 'cannot display visual' errors, so I went back to desktop but I saw nothing weird. When I refreshed in desktop (so not in the query editor, but in the 'design' area) I got the error 'sequence contains nog matching element'. I read that this is a bug that potentially came with a software update. Is there anything I can do to solve this issue? I included the error details below, and have reported the issue with full details to Microsoft.

Thanks!
Kind regards,

Lisan

These are the error details (it's super long so I couldn't include everything due to the character limit):

Feedback Type:
Frown (Error)

Error Message:
Sequence contains no matching element

Stack Trace:
System.InvalidOperationException
at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source, Func`2 predicate)
at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelSchemaSynchronizer.LoadInputFinalNameRewriter.GetFinalColumnNameFromSourceName(ITableInput tableInput, String sourceName)
at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelSchemaSynchronizer.LoadInputFinalNameRewriter.RewriteCrossTableReferences(IModelInput modelInput)
at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelSchemaSynchronizer.ApplyQuerySchemaToModel(IModelInput modelInput, IExtendedModelChangeScope modelChangeScope, Boolean requireFullDataRefresh)
at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.ApplyQueriesToModel(IExtendedModelChangeScope modelChangeScope, ModelSchemaSyncContext modelSchemaSyncContext, DataModelSnapshot preTransactionModelSnapshot, Boolean& runRelationshipDetection, List`1& newTableColumnPairs, HashSet`1& existingTableInputs, Boolean& upgradedModel, V3UpgradeStatus& v3UpgradeStatus, List`1& tableInputsExcludedFromSync)
at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.<>c__DisplayClass20_0.<ApplyQueryChangesAndCreateRelationships>b__0()
at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.ExecuteInTransaction(IExtendedModelChangeScope modelChangeScope, Func`1 action)
at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.ApplyQueryChangesAndCreateRelationships(IRelationshipLoader relationshipLoader, IExtendedModelChangeScope modelChangeScope, ModelSchemaSyncContext modelSchemaSyncContext)
at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.ProcessLoadInputs(IRelationshipLoader relationshipLoader, IExtendedModelChangeScope modelChangeScope, ModelSchemaSyncContext modelSchemaSyncContext)
at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.<>c__DisplayClass16_0.<PerformLoadAsync>b__3()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---

PowerBINonFatalError:
{"AppName":"PBIDesktop","AppVersion":"2.107.841.0","ModuleName":"Microsoft.PowerBI.Modeling.Engine.dll","Component":"Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelSchemaSynchronizer+LoadInputFinalNameRewriter","Error":"System.InvalidOperationException","MethodDef":"GetFinalColumnNameFromSourceName","ErrorOffset":"41"}

Snapshot Trace Logs:
C:\Users\lisan_dfs9\Microsoft\Power BI Desktop Store App\FrownSnapShotef7b70f3-ae5e-497e-9c9a-53a08313ba5d.zip

Model Default Mode:
Import

Model Version:
PowerBI_V3

Performance Trace Logs:
C:\Users\lisan_dfs9\Microsoft\Power BI Desktop Store App\PerformanceTraces.zip

[v-yingjl]

Same issue has been submited internal to confirm(ICM: 325094959), would update here as soon as possible if there is any progress about it.

Currently you can try to use previous version of Power BI Desktop to check that whether it still happens.

In addition, if you have used group by feature in Power Query, it may cause this issue, the fix will be released next week.

Best Regards,
Community Support Team _ Yingjie Li

[kstiegler]

I'm also having this error in the July and August (8/9 update) 2022 versions. I uninstalled Power BI Desktop and reinstalled the June 2022 version and I was able to refresh successfully from the 'design' area.