Custom Dataverse integration, error on Default Connection Setup

(11) Share

Report

Posted on by JacoB1234

Hi all,

I'm customizing the standard Dataverse integration. When resetting integration Table Mapping by selecting Use Default Connection Setup on the Dataverse Connection Setup age, I get the following error. See below for the full message:

"The Field does not exist. Identification fields and values: TableNo='50111',No.='0'"

The table 50111 is a custom virtual table. When i remove this table from the customizations, the error is still thrown. Resetting the connection also does not work.

Hope someone can help me!:)

If requesting support, please provide the following details to help troubleshooting:

Error message:
The Field does not exist. Identification fields and values: TableNo='50111',No.='0'

Internal session ID:
fa36b73a-7fea-4fa4-8b25-00b76fa0bb4f

Application Insights session ID:
c6308431-4290-4c0a-ae6d-0c285a7ff796

Client activity id:
cc8e1f75-3547-464c-871c-ce863eb44a17

Time stamp on error:
2025-07-31T14:00:23.8821150Z

User telemetry id:
de786224-5e9a-412c-92e8-2391981557e2

AL call stack:
"Integration Table Mapping"(Table 5335)."Integration Table UID Fld. No. - OnValidate"(Trigger) line 5 - Base Application by Microsoft
"Integration Table Mapping"(Table 5335).CreateRecord line 10 - Base Application by Microsoft
"Integration Table Mapping"(Table 5335).CreateRecord line 11 - Base Application by Microsoft
"Man. Integration Table Mapping"(Table 5380).InsertIntegrationTableMapping line 2 - Base Application by Microsoft
"Manual Int Mapping Events"(CodeUnit 5369).HandleOnAfterResetConfiguration line 10 - Base Application by Microsoft
"CDS Setup Defaults"(CodeUnit 7204).OnAfterResetConfiguration(Event) line 2 - Base Application by Microsoft
"CDS Setup Defaults"(CodeUnit 7204).SetCustomIntegrationsTableMappings line 2 - Base Application by Microsoft
"CDS Setup Defaults"(CodeUnit 7204).ResetConfiguration line 26 - Base Application by Microsoft
"CDS Connection Setup"(Page 7200)."ResetConfiguration - OnAction"(Trigger) line 5 - Base Application by Microsoft

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (12)

Answers (2)

Suggested answer

Jainam M. Kothari 15,631 Super User 2025 Season 2 on at

Like (4)

Report

May this can help : https://learn.microsoft.com/en-us/troubleshoot/power-platform/dataverse/data-integration/data-integrator-error-management

https://community.dynamics.com/forums/thread/details/?threadid=4663c63b-7553-4e6b-8306-256495e61be3

Was this reply helpful? Yes No
Suggested answer

Mansi Soni 8,907 Super User 2025 Season 2 on at

Like (6)

Report

Hello,

Hope this will give you some hints:

https://community.powerplatform.com/forums/thread/details/?threadid=a29cb6ec-314c-466b-9341-65f5e2c612c7
https://learn.microsoft.com/en-us/power-apps/developer/data-platform/reference/entities/importmap
https://learn.microsoft.com/en-us/fabric/data-factory/connector-troubleshoot-dynamics-dataverse

Regards,
Mansi Soni

Was this reply helpful? Yes No
Suggested answer

Akash Raj 121 on at

Like (5)

Report

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

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 95,329 Super User 2025 Season 2 on at

Like (3)

Report

Please remove the following portion of your custom code from codeunit, which appears to be still in your code.

PS:

Dynamics 365 Business Central: Customizing an Integration with Microsoft Dataverse (Integrate custom tables)

https://yzhums.com/17065/

Hope this helps.

Thanks.

ZHU

Was this reply helpful? Yes No
Suggested answer

Jeffrey Bulanadi 8,760 on at

Like (4)

Report
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:

First, manually remove any lingering entries in the Integration Table Mapping (Table 5335) that reference TableNo 50111. You may need to expose this table via a list page or query to clean it up.

Then, recompile and publish your extension to ensure all custom integration objects are properly registered.

Finally, retry the Use Default Connection Setup action. If the error persists, consider resetting the integration via the assisted setup guide instead of the manual page action.

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

If you find this helpful, feel free to mark this as the suggested or verified answer.

Cheers
Jeffrey

Was this reply helpful? Yes No
JacoB1234 84 on at

Like (3)

Report

Hi All,

Thanks for your answers!

I looked at all your suggestions but I'm still stuck.. I removed the Integration Table Mappings that were referencing the custom table, but still got the same error.

After that I removed all custom Integration Table mapping and unpublished my extension in Extension Management, but still got the error!

I'm really at a loss now, hope any of you has any ideas?

Was this reply helpful? Yes No
Verified answer

Mohana Yadav 60,993 Super User 2025 Season 2 on at

Like (4)

Report

Could you please open the 5335 table records from table information and filter Integration table id field with 50111?

Was this reply helpful? Yes No
Suggested answer

DAnny3211 11,397 on at

Like (2)

Report
Hello,

Thank you for sharing the details of your issue.

The error message:

"The Field does not exist. Identification fields and values: TableNo='50111';No='0'"

suggests that the system is attempting to reference a field or record in a custom virtual table (50111) that is either missing or improperly registered in the integration mapping.

Recommended Steps:

Verify Table Registration
Ensure that Table 50111 is correctly registered in the Integration Table Mapping and that all required fields (including primary keys and integration fields) are defined and published.

Remove Residual References
Even after removing the table from customizations, there may be residual references in the integration metadata. Try:

Deleting the related Integration Table Mapping entries manually.

Clearing any cached mappings or synchronization records.

Use Default Connection Setup Carefully
The "Use Default Connection Setup" action attempts to reset mappings based on standard configurations. If custom tables are involved, this may lead to conflicts. Consider:

Backing up the current configuration.

Manually resetting only the affected mappings rather than using the global reset.

Check AL Triggers and Events
The AL call stack indicates that the error occurs during the OnValidate trigger of the field Integration Table UID Fld. No.. Review any custom logic or event subscribers that may be interfering with the reset process.

Telemetry and Session IDs
If further investigation is needed, provide the listed session IDs and telemetry information to Microsoft Support for deeper analysis.

Temporary Workaround
As a workaround, consider commenting out or disabling the integration mapping for Table 50111 until the issue is resolved, especially if it is not critical to your current integration scope.

Please verify if this response was helpful.
Best regards.

Was this reply helpful? Yes No
Verified answer

Sohail Ahmed 11,136 Super User 2025 Season 2 on at

Like (4)

Report

This error is occurring because the custom virtual table (50111) is still referenced somewhere in the Dataverse integration setup, even though you’ve already removed the actual table or customization. Business Central is trying to access a field or record that no longer exists — typically during the process of resetting or reloading default mappings.

How to fix it:

1. Open table 5335 (Integration Table Mapping) via AL or Configuration Packages, and manually delete the record with TableNo='50111'.

> You can also filter by Table No. in the Integration Table Mapping page if accessible via UI.

2. Ensure that table 50111 is not referenced in codeunits (especially CDS Setup Defaults or Manual Int Mapping Events) or via a custom subscriber.

3. If you’ve removed the table but still face issues:

Go to Table 5380 – Manual Integration Table Mapping and check if 50111 is still there.

Also verify Integration Field Mapping (Table 5336) for any orphan mappings.

4. As a last resort (if UI fails), use a Page Extension or PowerShell/SQL (on-prem) to clear these orphan records.

This error usually surfaces because the "Use Default Connection Setup" tries to recreate all default mappings — including for deleted or renamed objects. Business Central does not always gracefully handle missing custom objects.

✅ Mark this as the verified answer if helpful.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 95,329 Super User 2025 Season 2 on at

Like (2)

Report

Then uninstall the extension, disable the settings, and then try setting them again.

See if that solves the problem.

Thanks.

ZHU

Was this reply helpful? Yes No