Dynamics Community Forum Thread Details

I am integrating Dynamics 365 Sales with Dynamics 365 Business Central with a unidirectional synchronization scenario, where only Opportunities are required to sync from D365 Sales to D365 Business Central.

Current Setup

Dataverse and Dynamics 365 Sales connections are fully configured and tested.
Both connections are working correctly.
Prior to synchronizing Opportunities, Contacts are being synchronized, as they are required dependencies.
Approximately 90% of the records are successfully coupled and synchronized.

Issue Description

For the remaining records (hundreds of Contacts), synchronization fails with the following error:

“The contact cannot be synchronized because the company does not exist.”

This error appears repeatedly in the Integration Synchronization Errors page (screenshot attached for reference).

Error Details

Error Message:
The contact cannot be synchronized because the company does not exist.
Internal session ID:
81136d5a-b5ba-4109-a547-0bac80550ebc
Application Insights session ID:
6844baec-f8e0-4c52-88a7-4314c9d7f4a7
Client activity ID:
55d3500b-a833-7558-95f2-987d903a071d
Timestamp:
2026-01-28T14:28:43.6880638Z
User telemetry ID:
0605565c-a8ee-44f6-8727-7a8706a0dc89

AL Call Stack (Key Area)

The error originates from the following standard Base Application code:

CRM Int. Table. Subscriber (Codeunit 5341)
- UpdateContactParentCompany
- OnBeforeInsertRecord

This suggests the failure occurs while resolving or validating the parent company/account for the Contact during synchronization.

Observations

Most Contacts sync correctly, indicating the integration configuration is generally valid.
The issue appears to be data-specific and related to Contacts whose parent company/account cannot be resolved or does not exist in Business Central at the time of sync.

Request for Guidance

I would appreciate guidance on:

How Business Central determines the parent company for Contacts during CRM integration.
Whether Accounts/Companies must be synchronized or coupled before related Contacts, will that resolve this Issue, but how most of contacts synced as they dont have companies as well.
Recommended best practices to handle such data scenarios in unidirectional sync (Sales → BC).

Any insights, documentation references, or similar experiences would be highly appreciated.

Thank you.

Categories:

Dynamics 365 general