Different ways of implementing Dynamics NAV and Dynamics 365 CRM Integration

Hi Reader,

Due to the boom of 345, a lot of clients have been looking forward to use NAV as well as CRM. Therefore, there is a need to create a link between the two. There are various ways in which this can be achieved depending on the client requirements, costing and convenience.

Here, I'll provide you with a gist of six ways in which an Integration of NAV to CRM can be achieved.



1. NAV Connector
Dynamics NAV already has a Connector for it to integrate CRM. There are CRM Tables (Filter Table Object *CRM*) in NAV. You need to configure the Connector (To know how to configure, email me and I'll provide you with the document). The only disadvantage is that the Integration will take place with a CRM Table in NAV and not with an actual one. For example, CRM Account will link to CRM Customer.

If you want your records to flow directly in Customer table then you will have to customize in NAV wherein whenever a record is created in CRM and flows to CRM Table, move it to NAV table automatically through a Job Queue or Codeunit.
To know more about it, refer: Connector

You can use this approach in the following scenarios:
    a. Low Budget, Time crunch and less/no customization
    b. Master tables and Sales Order Integration

2. Power Apps
It is a powerful tool which requires to Import CRM and NAV data sources. To know more about Power Apps refer PowerApps

You can use this approach  in the following scenarios:
    a. Good budget, Time crunch and no customization
    b. Master tables and Sales Order Integration
    c. Purchase and Maintenance of Licencing
    d. Records creation happens in low frequency
    e. Seamless Integration

3. Microsoft Flow
Microsoft Flow is configuration-based and you will have to select steps, conditions and Data sources that you need to use. To know more about MS Flow refer MS Flow

You can use this approach  in the following scenarios:
    a. Good budget and more time
    c. Purchase and Maintenance of Licencing. If you already have an Azure License, you will get MS Flow for free.
    d. Records creation takes time to reflect on an average of 1.5 mins per record. 

4. WCF Service 
WCF acts as a middle layer between CRM and NAV. Service needs to be created that will be added as a dll in NAV. CRUD methods will be created at both the ends depending on from where the to and fro operations will take place. The main job of the dll (WCF) service will be to carry this data to the respective products.

You can use this approach  in the following scenarios:
    a. Good budget, and more development Time
    c. Creation, Hosting and maintenance of WCF service
    d. Records created in bulk.
    e. Seamless and Bi-directional Integration

5. Add-on
There are various Customized Connectors available in the Market like eOne Solutions, Innovia, etc. The costing will, of course, depend on the Connector you choose according to your requirement.

6. Common Data Service 
Refer: CDS
It has the same scenarios as that of Power Apps.

I hope this blog was helpful and gave you a broader perspective of Integration.
Please write to me about your suggestions and queries in the comment section.

If you would like to have any of these Services, refer my website https://jyotsnanav.wordpress.com/ and email me at jyotsnaoberainav@gmail.com.

Thank you!