Skip to main content

MSDYN365BC - How to Connect VS Code with NAVUserPassword on-prem.

Hi Readers,

This is a follow up of last article where we did Configuration NavUserPassword in on-prem.

So after configuration to NavUserPassword you might not be able to connect to Visual studio Code.

In this article we will discuss about steps that you need to take so that we can use NavUserPassword on-Prem installation.

There are few changes that we need to do to connect VS Code with changes done in Service Tier.
What is the Issue?

1. Start your Visual studio Code.
2. Use Ctrl+Shift+P and Select AL: Go!
3. Choose the Folder where you want to save your extension.
4. Choose Target Platform.
5. Then Choose Your own Server.

If you try Download Symbol you may end of the error message as shown below.

Let's talk about how to fix this issue.

As we are using certificate with NavUserPassword, we configured our website with SSL we need to Enable SSL for VS Code.

Edit your Service Tier Configuration, Set Enable SSL, in Development Tab as shown below.
Restart your Service Tier.

  1. Next change that we will have to do is in Launch.json.
  2. Change Server from http to https.
  3. Change localhost to your certificate name that you are using in web browser.

Now try to Download Symbol and It should be download Symbol.

Last but not least, if you try to publish Extension, System will not be able to open Modern Client. 

For this we will have to upgrade web client Base URL in the Service Tier.

Open Service tier and Update - 

1. Web Client Base URL (in Client Services Tab).

2. Assign Value https://<Ceritifcate Name>/<Service Name>/Webclient

Restart the Service and Publish Extension. System will open Modern Client.

Hope this article helps you to setup NavUserPassword with Business Central #Msdyn365bc.

Let me know if you have any questions.

Stay connected, there is lot coming up.

Saurav Dhyani


Popular posts from this blog

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 - 

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.

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.