Keeping the CRM Healthy
Rikke Søndergaard avatar
Written by Rikke Søndergaard
Updated over a week ago

Keeping the CRM Healthy

Synchronising large amounts of data can slow down your CRM. To relieve the CRM as much as possible, APSIS One has taken the following steps:

Real-time Sync: CRM only sends the contents of the created or updated cards to APSIS One. To handle this message, APSIS One utilises its integration middle layer to handle the expensive operations related to consents and handling merging

Full Sync: Microsoft Dynamics is not responsible for sending any of the data to APSIS One as a part of a Full Sync. Instead, APSIS One downloads all of the contacts using Microsoft Dynamics' API endpoints for fetching paginated contacts. This puts the least amount of strain on the CRM since it only needs to respond to standard requests. Messages generated as part of a Full Sync are put in the same queue as the Real-time Sync messages, promoting consistency between Microsoft Dynamics 365 CRM and your APSIS One account.

Note that the Real-time Sync API does not accept any messages while contacts are downloaded for a Full Sync. This means that, for a short duration, a queue of messages might build up in the CRM. However, these are sent to APSIS One as soon as the Full Sync is completed.

All messages treated by our integration middle layer are put into a queue and processed over time, this keeps us from losing messages.

The service that processes these messages utilises an exponential backoff to all recipients (in this case, that's CRM environments) that give a response indicating a problem (problems related to network, problems related to high load, lack of response, etc.).

What's Next?

Did this answer your question?