Skip to main content

How Do I Connect VS Code to #msdny365bc Online.

Hi Readers,

Business Central is used by most of the customers and in this article, we will discuss about launch file of your extension.

Today we will talk about What are limitations and possibilities while connecting Visual Studio Code to Business Central SaaS Environments.

Most of us don't know much about Launch file. There are more settings which are not set by default. 

#msdyn365bc, #vscode 


 In Launch.Json, of your extension let's talk about important parameters - 

  • environmentType - The Valid Values are OnPrem, Production & Sandbox.
         ** You cannot publish and download symbols from Production. Choose Sandbox.
  • environmentName - Specify the environment name.
  • startupObjectType - Object Type that you need to run when publish extension. Valid values - Pages, Table, Report and Query. Default Value is Page.
  • startupObjectID - Object ID to run when extension is published.
  • startupCompany - Company Name which need to open when extension is published.
  • tenant - Specify the tenant ID of the environment. 

Other Important Stuff -

  • You can add multiple configurations in vs code, this will allow you to choose environment during download symbol and publish.
  • During connection you need to authorize, and credentials are cached in vs code. You should use Clear Credential Cache before connecting to another tenant. 
  • Extension Published via VS Code are tagged as Extension Type - DEV. These extensions will be removed after Major and Minor Upgrade by Microsoft.
  • Always publish your extension generated via CI/CD pipeline configured in Azure Devops or Github. 
Hope this helps, if not please watch session here.




Regards,
Saurav Dhyani

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    ---------------------------

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.

NAV 2013 Upgrade Part III - Data Upgrading.

Hi all, As per agenda we need to discuss the data upgrade in NAV 2013. The process is similar to what used to be till NAV 2009 R2 but with some changes. Let's start the process. Remember -  1) You can only upgrade a database to NAV 2013 from NAV 2009 SP1 / R2 SQL Only. 2) The Synchronization of users with SQL Server is no more required.