web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

Master Data Management - "Acc. Schedule Line" issue

(3) ShareShare
ReportReport
Posted on by 9
Hi,
I am trying to configure Master Data Management. For some tables like "G/L Account", "Dimension", "Dimension Values" it works without any problems, but when I add in the "Synchronization Tables" tables such as "Acc. Schedule Line", "Acc. Schedule Name" no entries are created in the "Master Data Initial Synchronization" page, so I can't start the initial synchronization and configure the couplings. Job Queue is created.  Selected tables are synchronized when new records from the master company are created in all subcompanies, but updates are not propagated because the BC tries to create modified records in the subcompanies instead of updating, resulting in a "record already exists" error. 
 
G/L Account works fine:
 
 
Account Schedule Line: added to "Synchronization Tables", no entry in the "Initial Synchronization"
 
But Job Queue is created
 
I have the same question (0)
  • Suggested answer
    Sohail Ahmed Profile Picture
    11,173 Super User 2026 Season 1 on at
    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.
     
    For more guidance, feel free to check: https://www.linkedin.com/in/sohailahmad897
     
     
    Mark below checkbox to make this answer Verified if it helps you. ✅
     
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,012 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 986 Super User 2026 Season 1

#3
Teagen Boll Profile Picture

Teagen Boll 659 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans