Skip to main content

NAV 2018 SERVICE OPTIONS RECAP

NAV 2018 SERVICE OPTIONS RECAP
In NAV 2018 there are many new options related to the NAV Service; some of them have already been introduced with the latest build \ cumulative updates for NAV 2016 and NAV 2017 and only updated \ modified; others are new and introduced by this release.
NEW POWERSHELL CMDLETS
There are also new powershell commands related to restarting and managing services.
CHANGE NAV SERVICE VALUES WITHOUT RESTARTING
The most interesting thing is as written in the “What’s New” it is now possible to modify the parameters of the service without restarting the instance. Great especially for multi-tenants environments. The product is therefore constantly evolving, under a brief RECAP of the most interesting service options to date.
SOME SERVICE OPTIONS
DATABASE CREDENTIALS

Database Credentials
Like old NAV releases… Windows or SQL Login for Database Authentication mode.
CREDENTIAL TYPE

Credential Type
Specifies the authentication mechanism for Microsoft Dynamics NAV users of this Microsoft Dynamics NAV Server instance.
BUILD RESTRICTIONS

Build Restriction
Specifies if Microsoft Dynamics NAV Server must allow, warn or prevent a connection from a client that is built with a different build number.
DEFAULT SERVICE AND CLIENT LANGUAGE
 
Default Client Language
Specifies which of the installed Dynamics NAV languages on the server instance will be used as the default language in the clients. Set the value to a valid language culture name, such en-US or da-DK.
Services Language
Specifies the global language version to use for text strings with SOAP and OData web services.
The value must be valid culture name for a language that is available for the Microsoft Dynamics NAV solution, such as en-US and da-DK.
DEVELOPMENT PORT & EXTENSIONS TARGET LEVEL

Development Port
The listening HTTP port for Microsoft Dynamics NAV Developer web services.
Extensions 2.0 – Target Level
“In Extensions 2.0, we have added a concept of ‘levels’ of extensions that are used to determine different classifications and capabilities of an extension package.
In VSCode development, this is something you can specify in the app.json file using the “target” property. This places a restriction on what is ‘allowed’ within the extension.
On the server side, you are given the ability to set the ‘level’ of 2.0 extensions that you want to allow to be publishable/installable. This gives admins control over what kinds of extension they want to have on their systems.”
In order the ‘level’ progress as follows:
  1. Personalization
    • Lowest current level, only allows for inclusion of UI objects like Profiles/PageCustomizations
  2. Extension
    • Default level, allows for all of the capabilities you would currently expect from an extension
  3. Solution
    • Unused at the moment, this (or something very like it) will be used to encompass the capabilities of ‘Embed’ apps in the future.
  4. Internal
    • Highest level, currently only for internal use à  NO EXTENSIONS, USE C/AL
SQL COMMANDS TIMEOUT (AND QUERY)

SQL Command Timeout
The contextual timeout for a SQL command.
SQL Connection Idle Timeout
Specifies the time that a SQL connection can remain idle before being closed. The value has the format HH:MM:SS.
SQL Query Logging Threshold
Specifies the amount of time (in milliseconds) that an SQL query can run before a warning event is recorded in the application log for the server instance.
If this threshold is exceeded, the following event is logged: Action completed successfully, but it took longer than the given threshold.
ODATA V4.0 ENDPOINT

Enable V4 Endpoint
Specifies whether the ODataV4 service endpoint will be enabled.
AZURE KEY VAULT ENCRYPTION

Client Certificate Store Location
Specifies the certificate store location for the Key Vault client certificate.
Stay tuned for next post !

#NAV 2018 #DYNAMICS

Comments

Post a Comment

Popular posts from this blog

The Difference Between Microsoft Dynamics NAV and AX

The Difference Between Microsoft Dynamics NAV and AX Microsoft Dynamics offers a variety of ERP solutions. You might say there is a solution for every purpose and every industry. Two of the offerings,  Dynamics NAV  and  Dynamics AX (now part of  Dynamics 365 ) share some of the same features so you might wonder: ‘what are the differences and which is right for my organization?’ Both ERP solutions are highly customizable, available in and adaptable to many languages and currencies used around the world. The two solutions can also be employed in a central location or across diverse satellite locations and are designed to grow as a business grows. Their industry-specific functionality can assure compliance with local and regional requirements. In short, both solutions could rightly be described as comprehensive and well equipped to manage complex requirements of supply chain and inventory. So, what is the difference? Is one better than the other for your...
Post a Comment
Read more

Quick Fix Visual Studio displaying NAV Report Layout as XML

I got this issue with Visual Studio 2015 Enterprise Edition.  Every time I open a Dynamics NAV report layout in Visual Studio, RDLC is rendered as XML file instead of visual layout with all the fields and tool boxes.  How the report layout looks:  FIX : In order to fix the issue you need to install  "Microsoft SQL Server Data Tools" .  To install "Microsoft SQL Server Data Tools" you need to go to  Control Panel   ->  Programs and Features  - >  Microsoft Visual Studio <Edition>  -> Change Or you can re run the installation setup.  From the features list, enable "Microsoft SQL Server Data Tools" option and proceed.  Once the installation is completed you are good to go. This time report layout will open in correct design layout.  Hope this helps you to resolve the issue. happy designing.  Please provide your feedback with a comment.  Thank you and Regards, +256775120005 ...
Post a Comment
Read more

Office 365 integration in a Dynamics NAV hosting environment

Office 365 integration in a Dynamics NAV hosting environment We from the Microsoft Dynamics NAV support team (Microsoft CSS) see an increasing number of support cases coming in related to Office 365 integration in a hosting environment. This range from the relatively new Edit in Excel feature or the relatively new Outlook Business Inbox to the more familiar Office 365 Single Sign On functionality. This blog post is intended to help you to first discuss the requirements with your customer, it may also help you to understand the difficulties. It should be relatively easy to implement these capabiltities, but since there are so many external components that require different configuration setup, we may end up in high labor intense support cases where we need to put all pieces together. This blog post will hopefully serve as a guide where we summarize all relevant documentation that is out there. Finally, we will showcase a typical environment with several Azure AD’s amo...
Post a Comment
Read more