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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Synchronization advice with ERP

(0) ShareShare
ReportReport
Posted on by

We have been using Dynamics Crm online for 2 years.
To adapt to our own Erp logic, it took :

  • Set the Crm (creation of custom entities, and fields, entity relations, view, forms...)
  • Code plugins to add missing features

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:

  • The development of C # plugins seems very risky in Dynamics, due to regular updates that can quickly become blocking. With the Crm online, it is very long and difficult to code without debugging.
    The plugins allow almost all synchronous processing that could be deported in our synchronization service. Easier to maintain but shifting data for short periods of time.

  • Can Azure and Logic apps help us? We do not use azure yet, but can we benefit from it?

  • The good old method of synchronization by import / export of csv files makes us a little afraid of its heaviness.

    Thanks in advance for your advices

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Radu Chiribelea Profile Picture
    6,667 on at

    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

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…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans