Small and medium business | Business Central, N...

Problem with synchronisation with using MDMS from BC22 wave1

(4) Share

Report

Posted on by SD-12070822-0

Hello

I have few problems with synchronisation, when I am using MDMS to synchronize the table - contact (5050), I am unable to make full synchronization and I can't synchronize contacts which have type (company)

Second problem I have is that when I am adding new contact on source company I get an error with message like below:

The field Lookup Contact No. of table Contact contains a value (MARK.0000372) that cannot be found in the related table (Contact).

Besides this is how looks like /show error call stack/ for that error:

Contact(Table 5050).TypeChange line 69 - Base Application by Microsoft
Contact(Table 5050).OnInsert(Trigger) line 38 - Base Application by Microsoft
/Integration Rec. Synch. Invoke/(CodeUnit 5345).InsertRecord line 3 - Base Application by Microsoft
/Integration Rec. Synch. Invoke/(CodeUnit 5345).SynchRecord line 85 - Base Application by Microsoft
/Integration Rec. Synch. Invoke/(CodeUnit 5345).OnRun(Trigger) line 3 - Base Application by Microsoft
/Integration Table Synch./(CodeUnit 5335).Synchronize line 49 - Base Application by Microsoft
/Integration Master Data Synch./(CodeUnit 7231).SynchIntegrationTableToLocalTable line 30 - _Exclude_Master_Data_Management by Microsoft
/Integration Master Data Synch./(CodeUnit 7231).PerformScheduledSynchFromIntegrationTable line 14 - _Exclude_Master_Data_Management by Microsoft
/Integration Master Data Synch./(CodeUnit 7231).OnRun(Trigger) line 17 - _Exclude_Master_Data_Management by Microsoft
/Integration Synch. Job Runner/(CodeUnit 5339).RunIntegrationTableSynch line 3 - Base Application by Microsoft
/Integration Synch. Job Runner/(CodeUnit 5339).OnRun(Trigger) line 5 - Base Application by Microsoft
/Job Queue Start Codeunit/(CodeUnit 449).OnRun(Trigger) line 17 - Base Application by Microsoft
/Job Queue Dispatcher/(CodeUnit 448).HandleRequest line 28 - Base Application by Microsoft
/Job Queue Dispatcher/(CodeUnit 448).OnRun(Trigger) line 19 - Base Application by Microsoft

Categories:

Dynamics 365 Business Central

I have the same question (1)

All responses (5)

Answers (0)

Suggested answer

Mohana Yadav 61,003 Super User 2025 Season 2 on at

Like (3)

Report

Did you enable Lookup Contact No field under contact table?

Please disable and try

Was this reply helpful? Yes No
SD-12070822-0 35 on at

Like (1)

Report

Thank you for that, it helped with one problem, but still I can not solve other one:

Problem with synchronisation, when I am using MDMS to synchronize the table - contact (5050), I am unable to make full synchronization and I can't synchronize contacts which have type (company). I tried synchronize after enable "Type" field but it did not help.

1 people found this reply helpful.

Was this reply helpful? Yes No
RV-02100924-0 4 on at

Like (1)

Report

Hey there,

Sorry to respond to such an old question, but did you ever resolve this? : "I am unable to make full synchronization and I can't synchronize contacts which have type (company)."

I'm experiencing the same issue; all contact in the target company are inserted as type = Person

Thanks in advance!

Was this reply helpful? Yes No
Suggested answer

Rishabh Kanaskar 6,150 on at

Like (1)

Report

Hi,

This error comes from MDMS limitations when syncing Contacts (table 5050).

1. Company-type contacts not syncing – By default, MDMS does not fully support synchronizing “Company” contacts because of dependencies on related Contact/Business Relation tables. You would need to customize MDMS integration tables or exclude these records.

2. Lookup Contact No. error – This happens when the Contact being inserted references a Lookup Contact No. that doesn’t exist in the target company. It usually occurs when the related person/company contact is missing or sync order is incorrect.
> Ensure related contacts (parent company or lookup contact) are synced first.
> Check your Integration Table Mappings – you may need to add or adjust filters.

Workarounds:
> Exclude fields like “Lookup Contact No.” from sync if not needed.
> Create a dependency sync: sync parent (company) contacts before child/person contacts.
> If required, extend the MDMS integration codeunit to handle missing lookup references gracefully.

MDMS contact sync is not fully plug-and-play for company/person hierarchies; it often requires custom mapping or extensions to avoid these lookup errors.

Thanks

Rishabh

Was this reply helpful? Yes No
Sumit Singh 10,193 on at

Like (2)

Report

Hi All,

This query was originally raised on 14th July 2023, so it’s possible that the issue has already been resolved by the original poster.

@RV-02100924-0, you may consider creating a new question instead. This will allow community members to respond without reopening an old thread, and it will also ensure your query appears in the current feed for better visibility instead of old query.

1 people found this reply helpful.

Was this reply helpful? Yes No