Skip to main content

Setup Development Environment with Business Central On-Premise Hosted on Azure

Introduction:
When you are using Business Central On-Premise, we might need to set up the Development Environment for AL Extension through Business Central Administration.
In this blog, I will be sharing how to set up Development Environment connectivity on your local device and Business Central On-Premise hosted on a Server using UserPassword.


Pre-requisites:

  • Understanding of Authentication 
  • Understanding of Business Central Administration
  • VS Code
  • AL Language Extension
  • Business Central On-Premise

Demonstration:

1. Set up Networking: 
i. Enable Port through Inbound Port Rules in Azure:

By default the Development Port required for Connectivity is disabled. Hence you will need to add the port in the Inbound Port Rules.



ii. Enable Port through Inbound Port Rules in Advanced Firewall Settings:
Add the port in the Inbound Port Rules in Firewall Settings.

Add Inbound Port in Firewall

2. Set up Development Configuration in Business Central Administration:
By default, Business Central Administration does not have Development Setup enabled.

You will need to enable the Development Endpoint and Debugger Endpoint. I have temporarily disabled the SSL Endpoint to check connectivity.

Business Central Administration for Development Endpoint
In order to connect to server the Authentication is to be used as follows-
Windows authentication can be used when your Server and Development PC is on same Azure AD
UserPassword is used when your Administration credential type is set to NavUserPassword and you can use the login credentials to connect to Business Central On-Premise.

3. Set up VS Code:
Once your  Business Central Administration tool is set, it's time to open VS Code and connect through the local server parameters. After you do AL Go> to Select Your Own Server. Refer to the screenshot below.

Launch.json

4. Download Symbols:
After VS Code setup, if you Download Symbols, your connectivity is set up correctly.
Sometimes you might need to clear the credential cache.

Connectivity Setup Successfully

Conclusion:

I hope this blog helps in setting up the connectivity of VS Code and Business Central On-Premise Server.
If there are any issues, feel free to contact me at olisterr@outlook.com.

Cheers!!



Comments

Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Universal Code Error and Resolution

Introduction: On Friday, May 12th, 2023, the Business Central On-Premise Production Environments started throwing universal code errors as follows. This occurred to every customer on a lower version of BC 19,20 and 21 irrespective of their localization, customization, and license. Pre-requisites:  Understanding of Technical Upgrade in Business Central On-Prem References: BC20 On prem. Universal Code requirement error after installing customer's license. - Dynamics 365 Business Central Forum Community Forum (40) Yammer : Dynamics 365 Business Central Development : View Conversation Root Cause: The certificate that signs Microsoft Base Application was expired. Errors started occurring if you Uninstalled, Installed Extensions, Restart Server Instances or for some even out of random started popping out. We first thought could be a license issue as we had fixed that before but this did not solve the issue. Resolution: Microsoft identified the issue and posted the following update The mi

How to resolve 'Edit in Excel' issues

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Editworkshe