The issue you're facing is due to how "Acc. Schedule Line" and similar tables behave in Master Data Management (MDM). These tables are considered complex/secondary data structures and are not always fully supported for two-way sync or proper initial coupling in MDM.
Key points:
1. No Initial Sync Entry: For some system/internal tables like "Acc. Schedule Line" or "Acc. Schedule Name", BC doesn't create entries in Master Data Initial Synchronization because these tables aren’t designed for direct synchronization in the same way as master data tables (like G/L Accounts or Dimensions).
2. Error: Record Already Exists: Since no coupling was created initially, when the master tries to push updates, it treats them as inserts — which leads to a conflict if the record already exists in the target company.
Recommendations:
Not all tables are fully supported by MDM — "Acc. Schedule Line" might require manual synchronization or custom integration logic via events, APIs, or job queue logic.
As a workaround, you can:
Manually pre-couple records using background logic or custom code.
Or handle sync using a custom synchronization extension.
I suggest contacting your Business Central partner for a tailored solution if you must sync these specific tables.
Mark below checkbox to make this answer Verified if it helps you. ✅
9
Share
Report
All responses (
Answers (
