We’ve been using the standard integration between Business Central and Dynamics 365 CRM. At first, we synced data from BC to CRM, and everything worked fine — the customer names were correctly pushed to CRM. Later, we changed the direction to sync from CRM to BC. After doing a “Synchronize Modified Records,” we noticed something strange: only a few customer records in BC had their Name fields messed up — replaced with things like a single dot, random letters, or even phone numbers. The data in CRM is still correct for those records, and the field mappings look fine. We’ve paused all integration jobs for now to prevent further issues. Has anyone else run into something like this where the sync from CRM to BC corrupts just a few records? Any ideas on what could cause this?
Good morning, afternoon, or evening depending on your location :) Hope you are well today! This is a serious issue, and you're right to pause the integration jobs. Based on your description, here's a breakdown of what could be causing the Customer Name field in Business Central to be overwritten with incorrect values during sync from Dynamics 365 CRM (Dataverse): Likely Causes 1. Incorrect Field Mapping Even if the field mappings look fine, it's possible that:
The CRM field mapped to the BC "Name" field is not the expected one (e.g., telephone1, description, or a custom field).
A custom field in CRM is mapped to the BC Name field unintentionally.
Action: Double-check the Integration Field Mapping for the Customer (Account) entity in BC. Look for any unexpected mappings to the Name field. 2. Data Type or Format Mismatch If the CRM field mapped to Name contains:
Symbols (like .)
Phone numbers
Random characters
…it may be due to data type mismatches or bad data in the source field. Action: Inspect the CRM records for the affected customers. Look at all fields that could be mapped to Name and see if any contain the corrupted values. 3. Custom Logic or Plugin Interference If there are:
Power Automate flows
Plugins
JavaScript on forms
…they might be modifying the data during or after sync. Action: Audit any custom logic in CRM or BC that could be modifying the Name field. 4. Partial or Failed Sync If the sync job:
Partially failed
Was interrupted
Had a schema mismatch
…it might have written incomplete or incorrect data. Action: Check the Integration Synchronization Errors and Shopify Log Entries (if applicable) in BC for any failed sync attempts. 5. CRM Record Ownership or Permissions If the CRM user running the sync doesn’t have full access to the correct fields, it might be pulling fallback or null values. Action: Confirm that the integration user has full read access to the correct fields in CRM. Recommended Fixes
Temporarily disable sync for the Name field in the integration mapping.
Correct the corrupted BC records manually or via script.
Re-map the correct CRM field to BC Name.
Test sync with a few safe records before re-enabling full sync.
Enable logging in the CRM Connection Setup in BC to capture future anomalies.
Note: I collaborated with Copilot to help craft this response for clarity and completeness. Hope this helps some!
Was this reply helpful?YesNo
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.
172
Share
Report
All responses (
Answers (
