With the release of NAV 2009 R2, we have endeavoured to prioritise features that many customers and partners have requested and this includes the ability to integrate NAV with CRM.
The approach we have chosen to provide integration between NAV and CRM is to use an existing solution called the Connector for Microsoft Dynamics. This solution enables the integration of NAV 2009 R2 with CRM 4.0 online or on premise.
As part of R2, we will provide out of the box support for synchronising common data such as customer, contact, sales order, and invoice, while also providing a means to enable synchronisation between any other standard or custom entities or fields that support specific business processes.
Let's take a typical scenario where integration between CRM and NAV can really support a business process:
The marketing manager uses CRM to manage her campaigns, opportunities and leads. When the leads are qualified they can be converted into a CRM Account. With integration enabled, this account subsequently becomes a customer in NAV. It's now possible for the sales team or customer service representatives to create orders in either CRM or NAV depending on their business process. The sales order will be integrated to NAV where the planning, payment processes, and shipping are handled, taking advantage of the core strengths of NAV.
When R2 ships we will be providing as standard, integrations between the following entities:
The Connector for Microsoft Dynamics uses web services to read and write data from CRM and NAV. It has two adapters for our solution that are designed to integrate with NAV 2009 R2 and with CRM 4.0. During configuration of the adapters, it is possible to specify which entities you want to integrate, which companies will be integrated, etc. so once the adapters are configured you can see a company-to-company integration with all the entities that you plan to integrate between the two systems.
The entities are synchronised through the use of maps which indicate which field in NAV relates to which field in CRM. For example, Customer Name in the Customer table in NAV may relate to the Customer Name in the Account entity in CRM. The systems can be kept in synch on a schedule that works for each entity. So for example, it might be that you want to synchronise your customer information from NAV to CRM every hour but you may only want to synchronise item data from NAV to create products in CRM on a weekly basis.
When the Connector runs, changes made to data in NAV that have been identified as data that will be integrated will trigger a field to be updated with a date/time stamp indicating that a change was made. The Connector can then query this date and look for changes via the web services since the last time the integration ran and write those changes to the destination system.
To view a recorded version of the Hot Topic session about Integrating Microsoft Dynamics NAV 2009 R2 with CRM 4.0, see the Partner Learning Center.