If you are doing Dynamics 365 Business Central development on your local (not Azure) containers, may be you want to have access to them from outside your local network without using VPN. And not only to BC Web Client, but even to API/OData and development endpoint. And of course you want to have them published with some trusted certificate to be able to use all the functionality like Business Central application, connection from Power BI connectors etc.
Today I would like to share a mini tip of Business Central, how to build extension (Package/Publish) without generating report layout files in VS Code.
When we create a new report, there are two main tasks to consider. First, we define the report dataset of data items and columns. Then, we design the report layout.
There are 2 kinds of apps: AppSource Apps and Per Tenant Extensions (PTEs). These apps can be installed in the global scope in two kinds of environments: Sandbox and Production. In Sandbox environments you can also install apps to the development scope (like what VS Code does).
I’m not writing a blog about every single (new) command in my “CRS AL Language Extension”. But this Sunday, I added an interesting one. One that I should have had created for a long time – but simply didn’t think of it, until Daniel (TheDenster.com) explicitly asked for it on GitHub.
Just imagine, you’re building an app, with many pages, and you want to build a page, test it, build the next one, test it .. . You kind have to:
– Publish the app
– Run the object after the app was published
I think I have mentioned before, that I strongly recommend partners to use the extension model and create extensions, which can be published, installed and upgraded much easier then code customizations.
Having said that, I know that there are partners out there for who AL code customizations will be the right stepping stone towards adapting an extension model.