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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Small and medium business | Business Central, N... / Business Central Integ...
Small and medium business | Business Central, N...
Suggested Answer

Business Central Integration with Real Estate CRM Lead Data Sync Issue

(4) ShareShare
ReportReport
Posted on by CU16071138-0 10

Hi Community,

We’re currently integrating Microsoft Dynamics 365 Business Central with a custom-built real estate CRM to sync lead and enquiry data between platforms. Most of the integration works fine, but we’re facing an issue where contact records created via web forms aren’t consistently pushing into BC

Here’s what we’ve done so far:

 

Verified API authentication (OAuth 2.0)
Confirmed the lead capture form is passing all required fields
Checked webhook logs no errors are returned, but BC doesn’t reflect the data

We’re also sanitizing all text fields, but wondering if custom fields like “Property Interest” or “Move-in Date” need specific mapping formats in BC?As a reference, this is similar to what we’re doing with property listing forms on realestateagentslondon.co.uk, where lead info is collected and synced into internal systems.Has anyone else done something similar and faced sync issues with custom lead fields or timestamps? Any suggestions would be great


     


 
Categories:
Dynamics 365 Business Central
I have the same question (0)
  • Suggested answer
    Jeffrey Bulanadi Profile Picture
    Jeffrey Bulanadi 8,760 on at

    Hi,

    Syncing lead data from a custom real estate CRM into BC can be tricky, especially when contact records created via web forms don’t consistently appear in BC despite clean webhook logs.

    Here’s what’s possible:

    • Webhook success ≠ BC insert success
      • Even if your webhook logs show no errors, BC may silently reject records if required fields are missing, improperly formatted, or if the integration user lacks permission. Check the Integration Synchronization Errors page in BC for hidden failures.
    • Custom fields like “Property Interest” or “Move-in Date”
      • These need to be mapped to valid BC fields or custom fields in your extension. If you’re using a proxy table or virtual entity, ensure the AL definitions match the CRM schema exactly — including data types and external names. For dates, use ISO 8601 format (YYYY-MM-DD) to avoid parsing issues.
    • Coupling logic matters
      • If your integration relies on record coupling, make sure dependent records (e.g., currency, unit of measure, or property type) are coupled first. Otherwise, BC may reject the contact record due to unresolved dependencies.
    • Try manual sync first
      • Use the DefineCoupling and UpdateOneNow actions to manually sync a few test records. This helps isolate whether the issue is with the data payload or the sync job itself.
    • Security roles in Dataverse
      • If you're using Dataverse as a bridge, confirm that the integration user has privileges to access custom entities. Missing roles can block sync even if the API call succeeds.


    Helpful references:

    Troubleshooting Synchronization Errors – Microsoft Learn
    Stack Overflow thread on sync issues with proxy tables
    Tips on Synchronizing Master Data – ERP Software Blog


    If you find this helpful, feel free to mark this as the suggested or verified answer.

    Cheers
    Jeffrey

  • Suggested answer
    YUN ZHU Profile Picture
    YUN ZHU 95,331 Super User 2025 Season 2 on at
    Sorry, I'm not an expert in CRM.
    Can these values be inserted normally when testing BC API in Postman?
    If there is no problem, it should be a problem with the CRM code.
     
    Hope this can give you some hints.
    Thanks.
    ZHU
  • Suggested answer
    Sohail Ahmed Profile Picture
    Sohail Ahmed 11,136 Super User 2025 Season 2 on at

    It sounds like the issue may be with how the custom fields are mapped. Are the fields like “Property Interest” and “Move-in Date” actually present and exposed in the API page on the BC side? Also, are you sending the date in the yyyy-MM-dd format? Even if the webhook shows no errors, BC might silently ignore records if fields aren’t properly mapped or permissions are missing.

     

    ✅ Mark this answer as 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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

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

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 3,143

#2
Jainam M. Kothari Profile Picture

Jainam M. Kothari 1,694 Super User 2025 Season 2

#3
YUN ZHU Profile Picture

YUN ZHU 1,067 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans