
We have been using Dynamics Crm online for 2 years.
To adapt to our own Erp logic, it took :
We synchronize a in-house Erp and Dynamics crm with a windows service (C #) running every 3 minutes. This service is hosted on an internal server and requests our database Erp (old oracle), and onlineCRM. The principle is simple : we regularly ask the Crm which entities have just benne created or modified to affect these changes on our Erp.
As soon as this processing is done, we do the same reverse work for other entities : changes to the Erp fills a table using triggers, these lines are then processed at the end of the synchronization service to mofiy our Erp.
The transition to Dynamics v9 requires a lot of work on the adaptation of plugins. The v8.2 update of 2017 had asked us for half a day of work. The v9 update of 2018 has already taken us a month, and it is not yet functional.
Several tracks:
*This post is locked for comments
I have the same question (0)Hello,
I think the Azure Service Bus could be an option here. You can configure CRM to post the execution context asynchronously to ASB and have a webjob there that does the business logic.
The advantage of this is following:
1. Execution context is posted asynchronously - so failing plug-ins responsible for the synchronization will not cause the transaction to roll back
2. Within your webjob you are no longer restricted to any sandboxed logic.
3. It takes load of the CRM Server - as processing and external calls are done outside of CRM
Hope this helps,
Radu