2
If the BC server's clock is ahead of the CRM server's clock then modifications in CRM are potentially ignored by the BC-CRM integration.
When an integration job runs but finds no records from CRM or NAV to process, then it updates the date filters on the Integration Table Mapping table with the current datetime from the BC server clock.
If a BC Server clock is 30 seconds ahead of the CRM server then there will be a 30 second window where records can be modified in CRM but will be ignored by the next sync job.
Suggested Fix:
In older versions of the integration, the Integration Table Mapping fields were only updated when a record was synced from that system. More specifically: “Synch. Int. Tbl. Mod. On Fltr.” should only be updated with a new datetime when a record is synced from CRM. When nothing is found, then the field should be left alone.
When an integration job runs but finds no records from CRM or NAV to process, then it updates the date filters on the Integration Table Mapping table with the current datetime from the BC server clock.
If a BC Server clock is 30 seconds ahead of the CRM server then there will be a 30 second window where records can be modified in CRM but will be ignored by the next sync job.
Suggested Fix:
In older versions of the integration, the Integration Table Mapping fields were only updated when a record was synced from that system. More specifically: “Synch. Int. Tbl. Mod. On Fltr.” should only be updated with a new datetime when a record is synced from CRM. When nothing is found, then the field should be left alone.
STATUS DETAILS
Completed
Business Central Team (administrator)