Is there a way we can integrate website with Dynamics NAV 2016 so that we can use XMLPORT Object in Navision to communicate with the Web Site.
We are a Microsoft Partner Company and our client is an E-Commerce company using Dynamics NAV 2016 as their ERP Solution. As the business has increased many folds for our client they now requires a Front End (in the form of a Dot Net Portal) which will be launched for Public use where the Sales Data should be captured in Dynamics NAV 2016. End User Website is created by client’s team which accepts the dataformat of XML only. Is there a way we can integrate this customer facing website with Dynamics NAV 2016 so that we can use XMLPORT Object in Navision to communicate with the Web Site.
Hi Jamie,
Do I understand it correctly, that your customer is having a “custom” website developed for them? And now that the webshop is created, THEN they start to look at how to integrate it with NAV and what to use XMLPorts to communicate with NAV?
Whereas this may be a rather “simple” solution, technically, then its not really a solution that I would suggest. A webshop integration is much more than file exchange. The issue is that today you have all your customers “business logic” inside NAV. This “logic” is a combination of both the setup and code inside NAV. I.e. all the rules you use to calculate customer specific pricing. If your customer is in B2B, then this may very often be some very complex calculations.
Unless you make a much tighter integration, than “just” XML files, then you often end up having the “recreate” the same business logic in your website. And make sure it’s updated, if you update NAV’s logic as well.
So while you may use XMLPorts to communicate, then using a combination of master data being updated using XMLPorts, then when it comes to the actual order interface, then here you should consider using NAV’s web services to communicate directly with NAV.
What [mention:16365c73cee442d1bc74db5cf6e4bd52:e9ed411860ed4f2ba0265705b8793d05] suggest is the other way around, which would only work if you wanted to let NAV control the communication and your webshop also had corresponding webservice. But normally you would want the shop to ask NAV for prices/products. Not the other way around. [:)]
Hi Jamie…
If your customer is already having a custom developed E-Commerce website then you can use NAV Web Services to make use of some functionality (Handling promotions, Pricing will be complicated).
We had developed a website www.gbiexpress.com . This site has complete integration with NAV System.
If the whole point is to configure something faster rather developing from scratch then its worth to try a DEMO with Data Masons-Vantage EDI eCommerce solution, Seems supporting a wide range of industries. Check if that fits your requirement.
You can Integrate a customer Facing Website with Dynamics Nav 2016 using the below steps.
Step 1 – Creating Navision Objects that integrated with a Dot Net based Website
NAV provides an option to publish Codeunits, Pages & Queries as SOAP / ODATA API’s. The published URL of the SOAP service can further be used to Create Input for Navision. For integration of a Website with Navision we can directly pass XMLPORT as an Input parameter to a Published Code unit via SOAP
Step 2 – Creating a Website that uses XML format as an input and send request in XML format
Default Web template can be used to create a website Visual Studio provides an option to create a website template with a default layout.
Step 3 – Creating a Web Reference for Web Service
Once the Website is created and the required files are loaded in the website folder created in step 2, Web reference needs to be added in the Website code which will be the SOAP URL published in Navision in step 1.
Step 4 – Deploying the Web site to use Navision SOAP URL for data exchange
Once the web reference is added in Dot net website, Next Website Build can be created followed by publishing the website. For testing the Code website can be started from Chrome or IE options available in Visual Studio.
You can also check this : www.paragyte.com/blog