When coding an app that uses Webservices to connect to the integration solutions, it is generally recommended that there is a Setup, which we can configure, where the Webservices are created as well as deleted.
Lots of web service vendors these days are tightening their requirement security protocols, SSL was removed back on the hearthbleed days, and not TLS version 1.0 and 1.1 are getting outed too. So suddenly NAV code that has been working for years stop working unless you change your client to select TLS1.2. Thankfully, there is a simple trick to choose the security protocol used by DotNet.
In this post I demonstrate how you can get XML data from a Web Service and then process the XML in NAV in order insert the needed values into a table.
I made the example using a service provided by the National Bank of Romania. This Web Service, gives Exchange Rates in XML format and I think it’s a good example for learning/practice purposes because it does not require a key and the XML is not too complex: