Integrating NAV 2009 R2 with CRM 4.0


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.

Samantha Scott

Comments (19)

  1. Stefano Demiliani says:

    Wonderful!

    What about price lists for products? Any synch or not?

  2. Peter says:

    Looks great, but where are version conflicts handled?

  3. Heather says:

    Wouldn't the client be connected to either NAV or CRM rather than the "connector" itself?

  4. freddyk says:

    Price lists are not synchronized in the default maps – you would have to add maps yourself to do that.

  5. freddyk says:

    Version conflicts are handled centrally in the Connector. Conflicts will be logged and reported in an e-mail, which can be send out on a pre defined schedule.

    Example is to do this weekly, meet and go through the conflicts.

    The conflicts are designed to be handled by the customer.

  6. freddyk says:

    The Client in the picture above is the CRM Connector Client.

    This is the place, where you setup your mapping rules and your schedules.

    Of course you will have the RoleTailored (or Classic) client for NAV and a browser or Outlook for CRM.

  7. miloradk says:

    This is great. Two things:

    1. What about deleted records?

    2. How can we synchronize lookup fields? Also, can we define sync. that will lookup through several entities in order to get some info. Or it is table to entity only. I know that there are basic formulas for handling data.

    thanks,

  8. freddyk says:

    Deleted records are also replicated. Whenever a record in NAV is deleted, CRM is notified about the deletion and vice versa. Of course the deletion can give an error (in which case there will be an entry in the log on the connector).

    Wrt. Lookup fields – a number of these are replicated in a map called Enumerated values / Picklists – but you can create other maps for integrating tables with lookup fields.

    The field in e.g. Customer pointing to the Currency for the customer would then be mapped to Currencies/Integration ID (which then points to the record in the lookup table)

    I hope this answers your qustion.

    /Freddy

  9. Martin says:

    Do you have to fully upgrade NAV 2009 databases for this functionality or will a binary (executable) upgrade suffice?

    I'm assuming the integration is designed based on 1 company to 1 CRM organisation? Or is it possible to synchronise multiple companies to 1 CRM organisation. Or multiple CRM organisations to 1 NAV company.

    Thanks in advance.

  10. freddyk says:

    There are some application changes for making CRM Integration work. Most of these changes are added objects but a couple of pages have been modified, the new database triggers are in codeunit 1 and a number of pages needs to be able to be exposed as web services.

    Standard is one company to one organisation – and if you do bi-directional integration I guess that is what you want.

    If you only replicate in one direction you could create maps which would collect multiple companies from NAV in one organisation in CRM or the other way.

    /Freddy

  11. Ìs it possible to download says:

    Is it possible to download this adapter? and are there any documentation somewhere?

    thanks.

    Morten

  12. navblog says:

    The adapter and documentation will be available with the release of Microsoft Dynamics NAV 2009 R2. blogs.msdn.com/…/microsoft-dynamics-nav-2009-r2-announcing-the-date-for-worldwide-general-availability-december-15-2010.aspx

  13. Heather says:

    what about CRM 2011.  Any integration to NAV planned?

  14. navblog says:

    Yes, we have plans to support the integration of NAV 2009 R2 with CRM 2011. The current version of the Connector for Microsoft Dynamics supports integration to CRM 4.0, the current version of Microsoft CRM. An adapter for integration will be available to coincide with the launch of Microsoft CRM 2011.

  15. Frank says:

    How do handll the integration into 2 companies within NAV

  16. freddyk says:

    In v1 of the Connector one company integrates to one organization.

    We are investigating what to do about this in v2.

    /Freddy

  17. tobia says:

    What to do about this?

    sounds very "uuups, like"

    No wonder apple is way ahead of Microsoft..

  18. Derek says:

    Any idea when the next release of the NAV – CRM connector will be due to handle multiple companies and CRM 2011 including claims based authentication?

  19. Chris Jones says:

    It says that Orders and Invoices are synched as standard, how about quotes as these are pretty similar in structure?

    If NAV uses Item Discount Groups with Customer Price Groups and Lists to determine the price of an item, does CRM somehow manage this as well?