Dataverse table access fails with TDS error 8657 in Fabric Dataflow

Hi everyone,

I’m experiencing an issue with the msdyn_project table when connecting to Dataverse from Microsoft Fabric Dataflow Gen2.

This is part of an existing production data pipeline that has been running on a scheduled refresh for several months.

Background

The existing pipeline has generally been working successfully. From time to time, we have experienced intermittent User Identity Failure during scheduled runs, but those failures have typically recovered automatically on a subsequent refresh.

I am now making an update to the solution because I need to bring additional data into the Lakehouse, Semantic Model, and Power BI report.

During testing, I created a new Dataflow Gen2 to connect to the same Dataverse environment. I can access and preview other Dataverse tables successfully, but I cannot preview the msdyn_project table.

Error

When I select msdyn_project, I receive:

The service has encountered an error processing your request. Please try again. Error code 8657. A severe error occurred on the current command. The results, if any, should be discarded.

Additional error details:

DataSourceKind = CommonDataService ErrorCode = 10478 Number = 40001 Class = 16 State = 1

Troubleshooting

I have confirmed the following:

• The existing Dataflow has been running successfully on a schedule for months.
• The Dataverse connection is working.
• Other Dataverse tables can be opened and previewed successfully.
• I created a new Dataflow Gen2 and reproduced the issue.
• The issue occurs specifically with msdyn_project.
• The error occurs when attempting to preview the source, before applying any Power Query transformations.
• Therefore, the issue does not appear to be related to my existing M code, Lakehouse destination, Semantic Model, or Power BI report.

Has anyone encountered Dataverse TDS error 8657 / 40001 specifically when accessing msdyn_project through Microsoft Fabric?

I’m looking for recommendations on how to diagnose the issue and determine whether a specific field, metadata change, or service-side issue is causing the failure.

Thank you!