Skip to main content

MSDYN365BC - Whats new in Microsoft Dynamics 365 Business Central Service Tier.

Hi Readers,

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.

In this article, we will discuss what new options that are added or changed in Service Tier with MSDYN365BC (on-Prem).

Click here to access all published Article about MSDYN365BC.

1. In General Tab following New Options are added.
  • Century Cutoff for 2-Digit Years. - Specifies the last year of the 100-year range for representing two-digit years. This setting determines how two-digit years in dates that are entered in the client are interpreted. For example, the default value is 2029. This means that two-digit years are interpreted as a year between 1930 and 2029. If you set the value to 2050, two-digit years are interpreted as a year between 1951 and 2050.
  •  Diagnostics Trace Level for External Proxies. - Specifies the diagnostics trace level for external proxies. Valid Options are shown below.



  •  Enable Session Creation While Sync Pending And Data Upgrade - This setting existed in NAV 2018 but only for Sync Pending. In MSDYN365BC it also includes Data Upgrade.
  • Non-Interactive Sessions Log Retain Time Interval - A new setting instead of those confusing session timeouts. Specifies the time interval that background and web service sessions remain in the Session Event table before they are deleted. This value has format d.hh:mm:ss.
  • Server Instance Name. - This setting was available in NAV 2018 also but with MSDYN365BC we can change the name of the service tier using this parameter.
  • Session Event Table Retain Time Interval - A new setting that Specifies the time interval that sessions in the Session Events table remain before they are deleted. This value has format d.hh:mm:ss.

2. New Tab Extension.
  • Overwrite existing translations - Specifies whether to overwrite existing text translations in the base application with text translations that are included in extensions. More about Translation - MSDN


3. In Database Tab following settings are added.
  • Search Timeout - Specifies the amount of time that a search operation on lists in the client will continue until it is terminated. The value has the format HH:MM: SS.
  • SQL Bulk Import Batch Size - Specifies how many SQL memory chunks a data import must be distributed across. A small number increases the number of network transfers and decreases performance, but also lowers the amount of memory that the server instance consumes. If the database is on SQL Server 2016 or later, a low value of Bulk batch size can lead to large data files. To not use batching, specify 0. 


There is some other settings/configuration added in Microsoft Dynamics 365 Business central which are not available in the console but can be updated/modified from the configuration file.

1. NonInteractiveSessionsLogRetainPeriod - Specifies the number of days that background and web service sessions remain in the Session Event table before they are deleted. Setting this value anything other than 0 will override the value in NonInteractiveSessionsLogRetainInterval.

2. CacheUserDefinedWebServices - Specifies whether user-defined web services are cached.

3. ExternalNavAppDeploymentEndpoint - Endpoint for the external nav app publisher API.

4. ExternalNavAppDeploymentRequestTimeout - Timeout for the external nav app deployment API.

5. ReportSettingsLookupForm - Page id for manage report settings. Default Value 1560.

6. HybridDeploymentProxyEndpoint - Endpoint for the hybrid deployment proxy API.

7. HybridDeploymentProxyRequestTimeout - Timeout for the hybrid deployment proxy API.

Hope you find the information useful. Stay Tuned for more.

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

RTC Report It is not possible to instantiate the Visual Studio bridge.

Hi all, As a Navision developers I have Multiple Versions of Navision running in single Machine. As discussed Earlier in the post how to run multiple Version of RTC in single machine. So my machine have following details for RTC Versions - NAV 2009 R2    - is installed. NAV 2009 SP1  - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 SP1 IN\ NAV 2009         - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 IN\ This approach has been working great for execution of Classic and RTC Clients. However, after installing Dynamics NAV 2009 R2, if i tried to view the Layout for an NAV 2009 SP1 Report i was getting the following error: ---------------------------  Microsoft Dynamics NAV Classic  ---------------------------  It is not possible to instantiate  the Visual Studio bridge.  ---------------------------  OK    --------------------------- After searchi...

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.