You’re offline. This is a read only version of the page.
Hi,
I haven't any experience working with Dynamics integration until now and am surprised at how customised and convoluted it appears to be.
I am late on the scene and have found that the NAV vendor has chosen Kingsway Soft to interface between NAV and CRM.
I'm told that the interface pieces have been developed from the ground up - and I've heard of issues like:
* we should have used a flag here to indicate a record has been copied over
* we should have used a date-time on this record to manage changes on each side of the fence during the sync process
* some of these records are being missed - I think we need to change the logic to include a primary key
I'm puzzled about the need to re-invent the wheel (if that's what is happening) when integrating between two highly regarded, well used products.
Does the problem lie with the selection of Kingsway Soft or - if the standard Microsoft connector was used, would the integration logic still need to be developed from the ground up?
*This post is locked for comments
I have the same question (0)
Generally there is a standard connector offered by Vendor out-of-the-box, and its availability depends on the versions of both products in use. From NAV version to version it gets better and better. For NAV 2016, I would say it is still a lot underdeveloped, however in 2017 and 2018 it is a lot more usable.
Please refer here: docs.microsoft.com/.../integrating-dynamics-crm-in-dynamics-nav for current integration options and here docs.microsoft.com/.../how-to-prepare-dynamics-crm-for-integration for item availability matrix.
Here is some previous discussion on the topic:
community.dynamics.com/.../283000
community.dynamics.com/.../249073
Generally, standard integration has by default fewer functionality and features compared to dedicated 3rd party solution - but this is natural for many other dedicated solutions, available on the market.
Share
Report
All responses (
Answers (
28,094
