Saturday, September 15, 2018

Business Central Administration - Extended Feature

Extended feature of Business Central Administration

Dear Friends, I have something to share with you. Many of us have already gone through these setups and must have seen it while configuring service. Still, curiously I am sharing these interesting features to you...

Have a look on General tab of Service console, you will notice few additional feature and some of change in value setting:

1. Century Cutoff for 2-Digit Years: <New Feature>

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.

2. Diagnostics Trace Level for external proxies: <New Feature>

Specifies the diagnostics trace level for external proxies.

3. Non-Interactive Session Log Retain Time Interval: <New Feature>

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. 

4. Server Instance Name: <New Feature>

Name of the server instance to connect to (for client) or listen to (for server). 

Now we can change the service name as well. 

5. Session Event Table Retain Time Interval: <Change in Feature>

Specifies the time interval that sessions in the Session Events table remain before they are deleted. This value has format d.hh:mm:ss.

Compare to previous version, it was only month. 

Another changes you can see in Database tab:

1. Search Timeout: <New Feature>

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.

2. SQL Bulk Import Batch Size: <New Feature>

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.

Next changes you can see in Report tab:

1. Enable Application Domain Isolation: <New Feature>

Specifies whether application domain isolation is used for rendering custom RDLC layouts. This setting pertains to on-premise installations only. Enabling application domain isolation provides a more secure and reliable environment for processing custom RDLC layouts; however, it can considerably increase the time it takes to render reports. This is the default setting. Disabling application domain isolation can improve the rendering time but might have a negative impact on security and reliability.

Friends, now time to have a look and experience the new addition and changes.

Friday, September 14, 2018

How to install Microsoft Dynamics 365 Business Central for Development

How to install Microsoft Dynamics 365 Business Central on-premise version for Development

Step 1: Run Setup with Administrator privileges

Step 2:  Select Next from below screen

Step 3: Accept Microsoft License Terms

Step 4: Click on "Advance Installation Options" for on-premise

Step 5: Click on "Choose an Installation Options" for Developer

Step 6: Click on "Developer": If you haven't click Customize then you will require to complete Setp 9 to Step 11. Below illustration is with "Developer" option click (without Customize):

Step 7: Define Installation Location, Server Details, Ports (Change if another instance of NAV is already using those.), SQL Server Details, Web Server Component & Help Server Details.

(Recommended to change all ports if other NAV versions install and defaults port are already in use. Make sure you have MS SQL 2016.)

Step 8: Wait till Setup will finish the Installation. If Setup end with error message then check the message and fix accordingly. Error generally come with insufficient privilege, missing prerequisites, etc. 

Note: Better to install MS SQL 2016 in advance before installing Business Central.  

After successful installation, you will require to install Dynamics NAV Client for C/AL Development Environment & RTC Client.

Step 9: Below setup will require to run if we haven't chosen "Developer" --> "Customize...". If not then, run setup with Administrator privilege again and click on "Add or remove components"

Step 10: Enable / Add all required / missing component from screen

Step 11: Click "Next" to finish the installation

Bingo! You have now completed almost installation for Development with AL (through Visual Studio Code) & C/AL (with C/SIDE Development Environment). 

Enjoy Legacy & Advance environment of Microsoft Dynamics 365 Business Central.

Thank You! The Dynamics NAV journey not stopped here and a new era begins here with Dynamics 365 Business Central. In both case, Dynamics keeps moving towards future...