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
Post a Comment