Hi,
The error you're seeing typically occurs when the system tries to validate a mapping against a custom table that no longer exists or is improperly registered. Even if you’ve removed the table from your customizations, the integration metadata may still reference it internally.
The error message:
"The Field does not exist. Identification fields and values: TableNo='50111',No.='0'"
suggests that the system is trying to resolve a field from your custom virtual table (50111) during the reset process, but it can’t find a valid record. This often happens when the integration table mapping still contains a reference to that table, even if the table object has been deleted or unpublished.
To resolve this:
If you’re customizing the Dataverse integration, make sure your virtual tables are correctly defined and that each has a valid primary key and field mapping. Also confirm that your integration user has access to the corresponding Dataverse entities.
Helpful References:
Connect to Microsoft Dataverse – BC
Customizing Dataverse Integration – Dynamics 365 Lab
Dataverse Connection Setup Guide – Dynamicssquare
Hi @HT1980
If you're encountering this error in the Sandbox environment, please verify whether the dependent extension has been deployed. This could be a potential reason for the issue.
If the extension is missing, kindly install it and the error should be resolved.
Regards,
Akash Raj
Jeffrey Bulanadi
3,878
Sohail Ahmed
3,583
Super User 2025 Season 2
Jainam M. Kothari
3,175
Super User 2025 Season 2