NAV 2016 Built-In Integration vs. Scribe Insight for Dynamics CRM
I have messed around with the NAV 2016 built-in integration for Dynamics CRM and here are my thoughts.
Built-in integration: It is built-in, no installation 🙂 (You need to manually import the CRM solution in CRM)
Scribe Insight: Needs to be installed manually
For performance then it is better to have dedicated integration server, specially for solutions with many users and many transactions, that needs to be processed between the two systems.
I have tested the built-in integration in my demo enviroment, so it is hard to tell how it will perform in production environment, where there are users in the system and where the NAV has been customized with custom business logic.
What I like with the built-in integration, is that they have added CRM buttons in the NAV ribbon, you can select one customer in NAV and view it in CRM.
There is also button where you can select specific customer in NAV from CRM and synchronize it to NAV instantly.
In CRM, they have added ‘Dynamics NAV button, clicking on it will open the customer in NAV WebClient.
Built-in integration comes with default setup that includes:
This setup also includes the buttons in NAV and CRM ribbon.
You can view orders from CRM in NAV and select which one you want to create in NAV, the list will only show orders that are not in NAV, this is nice feature.
You can also view CRM data, without having the data integrated with NAV.
For an example, you can view CRM opportunities in NAV.
You can also see customers stats in NAV from CRM.
And also the other way around:
Scribe Insight Template includes:
To modify the default setup,add new table or add new field to integrate, you need to do this using codeunits in NAV.
This can be done by NAV developers.
Here is an sample, how much coding is required to make changes:
To modify integration in Scribe, you can do this using the Scribe Workbench, no coding required, it is done using the visual editor.
This can be done by Scribe consultants and also super-users.
It takes less time to customize integration in Scribe.
NAV 2016 built-integration is specific for NAV and CRM.
Scribe Insight can be used for other integrations also.
You can have many integrations running on the same Scribe Insight.
Scribe can also be used for importing data in CRM and exporting.
You can use built-in integration and also Scribe Insight on the same solution.
For an example, you can use Scribe Insight for synchronizing data between the systems and use built-in integration for viewing CRM data in NAV without it synchronizing data.
Hybrid solution 🙂
Built-in integration: It comes with NAV, no extra cost for the license.
Scribe Insight: Starts from 3.000 USD
The built-in integration is free, but you need to calculate and compare how many hours you will need to customize the integration.
For an example, adding new field in codeunits will take more time than adding new field using Scribe Insight.
There is still plenty of different scenarios that I haven’t tested.
I will update this post when I have done more testing.
But I can already write this:
Will I continue to use Scribe Insight for Dynamics CRM and NAV integration? Yes
Will I use the built-in integration in NAV 2016? Yes
Will I use both of them in same solution? Yes, where it makes sense to do so.
What is the best solution for you? It depends on your requirements, I strongly recommend to get your requirements analyzed and find the best solution for you.
If you have any questions or want something included in the next post, you are welcome to contact me.