If you are reading then you know that we have already installed Microsoft Dynamics 365 BC (on-prem) and also checked where components are installed and all available client options. We also discussed connecting to VS Code.
We, the Microsoft Dynamics NAV Support Team in the Customer Service and Support (CSS) department, see from time to time cases asking for the Service Principal Names (SPN) that are required for Dynamics NAV Web Services (WS) to run properly on a three-tier environment with Kerberos enabled.
In this article, we will try to discuss and find out changes between Microsoft Dynamics NAV 2017 and Microsoft Dynamics NAV 2018 Service Tier Panel. We will visit tab by tab and try to identify what new added in the service tier panel and try to figure out what those new options can be used in the system
We generally use SOAP or REST API to integrate NAV system with any third party software, In NAV 2018 a new feature has been introduced for REST API interface, it Includes 44 entities providing access to business entities related to core financial functionality, such as company information, journal entry, customer and vendor management, sales and purchasing documents, and financial reporting.
All functionalities are working on LOCAL and REMOTE machines when you have the administration rights to that machine.
Installing, Uninstalling, Start, Stop, Restart and dynamic change of settings like Portsharing, Account, start mode and settings in the CustomSettings.config of the Service Tier.