Pieter de Jong Pieter de Jong
Nov 2, 2016 8:00:03 AM

In recent months, I’ve come across many posts and articles about integrations between Microsoft Dynamics CRM or Salesforce and Microsoft Dynamics AX 2012 or Microsoft Dynamics 365 for Operations. Often, the writers suggest that the best integration option is using the Microsoft Common Data Model, a secure database for storing and managing business entities, together with Microsoft Flow, which lets you build automated workflows between apps and services. However, that approach is not yet entirely stable and does not keep your data in sync. Can these integrations be accomplished in other ways?

At STAEDEAN, our Connectivity Studio solution, thoroughly tested and proven in many customer integration scenarios, is effective in Dynamics AX 2012 environments and is now also certified for Microsoft Dynamics 365 for Operations. By using this solution, we easily set up an integration with Salesforce CRM or Microsoft Dynamics CRM.

There are two main ways to achieve this integration. We can use the services technology directly, which involves some critical details and requires a higher level of technical expertise. Or, we can build the integration by means of an ODBC connection, which is extremely simple to set up. Instead of spending days on development and resolving technical challenges, you can have a new integration done within minutes.

Most of us working in complex Dynamics ERP environments are used to ODBC—it’s a well-known interface, designed for optimal interoperability, easy to understand and implement. In the background, ODBC accesses the available services, which means it is safe and predictable. It’s not a hack that bypasses existing functionality.

Connectivity Studio helps IT departments get their work done efficiently. You can configure integrations without the need for X++ development skills on your team. This makes good sense especially for recurring integrations.

If you want to give our solution a try, or have feedback and questions, please contact  STAEDEAN.

Pieter de Jong Pieter de Jong
TI_LOGO_TI-Logo-color andAXP_365

have now rebranded to