web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Blogs / My NAV Notes / Business Central System Con...

Business Central System Configuration Dynamically Updateable (NST Settings)

Community Member Profile Picture Community Member

As we all know: if you configure the Business Central service tier from the Administration tool you could receive this message when clicking on the Save button:

To take the new settings into effect the service needs to be restarted, this needed when changing for example the database name or enabling SOAP or OData webservices.

But some settings are now what Microsoft calls ‘dynamically updateable’. This is a really nice feature, because changing certain settings now don’t require a restart. For example if I change the setting ‘EnableFullALFunctionTracing’ for example you will now get new information from both the Administration tool and ofcourse from the PowerShell cmdlet:

 ‘ApplyTo’ Message from the Business Central Administration Tool  ‘ApplyTo’ Message from the Business Central Administration Shell

Some further investigation learned this new parameter has 3 options:

  • All
  • ConfigFile
  • Memory

Copied this from Microsoft Docs:

ConfigFile or 0: Saves the change to the configuration file of the server instance. The change will not take effect until the server instance is restarted.

Memory or 1: The setting change is just applied to the server instance’s current setting state. This is only applicable for server settings which support dynamic updating. If the specified setting is not dynamically updateable this command will fail.

All or 2: Applies the change to the server instance’s current setting state (in memory) and to the configuration file. This is only applicable for server settings that support dynamic updating. If the setting does not support dynamic updating, the cmdlet will fail with an error. The change will not be applied to the current session or the configuration file.

Finally an example to use this parameters in VS Code, PowerShell ISE or the Business Central Administration Shell for example:

Import-Module 'C:\Program Files\Microsoft Dynamics 365 Business Central\130\Service\NavAdminTool.ps1'
Set-NAVServerConfiguration -ServerInstance 'BCS130Test' -KeyName 'EnableFullALFunctionTracing' -KeyValue 'True' -ApplyTo 'All'

Keep in mind that only certain settings are dynamically updatable. Most settings still require a restart after a change.


This was originally posted here.

Comments

*This post is locked for comments