How It Works

On the server side you normally have a Microsoft Dynamics NAV 2009 R2, 2013, 2013 R2, 2015, 2016, 2017 or 2018 Server. These versions come with a new component, which is the Business Web Service, which provides web service access to the published pages and codeunits of the NAV system.

The configuration stored centrally inside the NAV database. This MobileNAV Configuration is basically containing metadata information about the published pages and codeunits for the MobileNAV client. The idea is that this configuration will describe all the MobileNAV related configurations or customizations and on the first login of the client he will download the configuration from the server and once the configuration has been downloaded to the client side, than he will build up the user interface regarding to this configuration. So in that case you can easily customize the solution and you can roll out all customization to the client’s devices.

The MobileNAV client is communicating with the MobileNAV Add-on first, to download the MobileNAV configuration. Once it the client downloaded the configuration, the client can consume and exchange data directly with the page web services of the NAV. MobileNAV client uses HTTP as a protocol, so the firewalls and proxies will supports this kind of communication. The authentication is NTLM, so you have to have Windows logins for your mobile users. MobileNAV also supports NAVUserPassword users from NAV version 2013 or above. You can protect the communication channel with SSL encryption. This is recommended for production environments.