Skip to main content

NAV 2013 R2 - Configure a Shortcut to point a Specific Database.

Hi all,

Consider a scenario where your client have two database -

a) Live Database. (Hosted on Port No. 7046)
b) Test Database. (Hosted on Port No. 10046)

Now Client wants to have two shortcuts on User Desktop which should point to Live and Test Database Respectively. User does not require to Select Server and change the database.

Question 1 - HOW RTC CLIENT POINTS TO DATABASE ?

- When you click on Windows Client,by Default it tries to connect to Last Successfully Connected database Service.



Question 2 - How it Does This ?

- The information about last successfully connected database service is stored in User Folder of your computer. RTC Clients reads that file and connect to the database.

Question 3 - Can we Change that File?

YES

Question 4 - Can we bound the RTC Shortcut to use a specific configuration file?

YES

Let's See answer of all the Questions that we have in Mind.

- The Configuration file that client use to connect to service is stored at -
C:\Users\<User Name>\AppData\Roaming\Microsoft\Microsoft Dynamics NAV\71

- File Name - ClientUserSettings.config

- The Configuration file Look like as shown below.



Let's see how can i make a RTC shortcut to point a Other configuration file than standard.

- Copy the configuration file from C:\Users\<User Name>\AppData\Roaming\Microsoft\Microsoft Dynamics NAV\71 to Say D Drive and Rename it to any name you want or keep it as it is. (I am keeping the file name as same)

- But i change some parameters like service port number, service name so that my shortcut points to a different database.



- Create a shortcut at desktop.

- Go to Properties of that shortcut.

- In Target Window you will see something like this (Default Path of Client) -

"C:\Program Files (x86)\Microsoft Dynamics NAV\71\RoleTailored Client\Microsoft.Dynamics.Nav.Client.exe"

- Just Add following Line after the End of Target -
 -settings:"d:\ClientUserSettings.config"

- Your complete Path in Target should be Like -
"C:\Program Files (x86)\Microsoft Dynamics NAV\71\RoleTailored Client\Microsoft.Dynamics.Nav.Client.exe" -settings:"d:\ClientUserSettings.config"

Hit Apply and Ok.

Now whenever you click on the Shortcut and if service is running fine, it will point to the database as per your configuration file in D Drive.

I hope you will be able to create as many shortcuts as you want.

Regards,
Saurav Dhyani
saurav-nav.blogspot.in

Comments

  1. Hi Saurav,

    Can we point the shortcuts to two different company in a same database

    ReplyDelete

Post a Comment

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.