Facing an issue while connecting with Dataverse

[mbilal079]

I'm getting the Opportunities table from Dataverse but getting the below error.

DataSource.Error: Microsoft SQL: Invalid column name 'accountid'.
Invalid column name 'accountidname'.
Invalid column name 'accountidyominame'.
Invalid column name 'contactid'.
Invalid column name 'contactidname'.
Invalid column name 'contactidyominame'.
Time: 2022-10-04T09:52:20.3765490Z
Details:
DataSourceKind=CommonDataService
DataSourcePath=seedspace1.crm6.dynamics.com
Message=Invalid column name 'accountid'.
Invalid column name 'accountidname'.
Invalid column name 'accountidyominame'.
Invalid column name 'contactid'.
Invalid column name 'contactidname'.
Invalid column name 'contactidyominame'.
Time: 2022-10-04T09:52:20.3765490Z
ErrorCode=-2146232060
Number=40000
Class=16

How can i fix that?

Any help?

Thanks in advance.

@amitchandak  @Greg_Deckler  @parry2k 

[tnguyen]

I have the same issue and "Refresh Preview"  doesn't work.

Even I try to connect to make a new file access opportunity table via  Dataverse and have the same error message
Looking for a solution.

Thanks,

[marine_adz]

Experienced the same problem, possibly since activating 2022 release wave 2.

Data seemed to load fine in Power BI Desktop but wouldn't refresh in the service.

Managed to solve it by identifying several 'Removed Columns' steps in 'Transform Data' queries and removing the problem field(s) - it means they now show in the data, but eliminates the data refresh problem.

[Russ55]

Hello @mbilal079, would be glad to hear if you manage to get this sorted. I'm having exactly the same error with the same column names on our dataverse opportunity table. I can't connect to them using PowerBI desktop or Excel. I can connect to it on our Dev environment but not on our UAT or Production environments. 

[v-jingzhang]

Hi @mbilal079 

Try opening Power Query Editor and clicking "Refresh Preview" in it. 

Best Regards,
Community Support Team _ Jing
If this post helps, please Accept it as Solution to help other members find it.

[PaulDG]

This was the solution for me- thanks, I believe I deleted a couple of columns in the datverse table that was throwing out power BI. Didnt think to refresh the query as I just created it but it must have been working of a cached schema or something 

[mbilal079]

Hi @v-jingzhang 

Thank you for your response.

I have refreshed it a couple of times but still having the same issue.

Thank You!.