In the cloud, we must play by Microsoft rules, but what are the rules and limits? In this video, I take a look at the current limits and what look at the impact of current projects. Check it out:
As you might know, there are two kinds of extensions in Business Central world: AppSource Extensions and Per-Tenant Extensions (PTE).
When you have finished developing and testing your tenant customization, you must deploy the extension (.app file) containing the customization to your customer’s production tenant. Recently I saw some discussions about whether it is possible to deploy a same PTE in the same version into different Tenants/Customers?
Since Microsoft does not provide a lot of information for this, I am not sure if the content I write next is related to the title, but it may bring readers a lot of new information is not bad.
Okay, when you open the My setting in BC19, you will see an additional item.
Some news if you use Cloud Migration Tool (aka Intelligent Edge) in Business Central. And not very good news.
Migration scheduled runs are not working now. Honestly they totally disappeared from functionality. I created support request to Microsoft and answer is “they’ll back in release 2021 wave 2”. Stunning. I understand that only few customers use this in production (on my mind) but now we have to run migration manually when we need data from on-premise in SaaS.
Snapshot debugging allows a delegated admin to record AL code that runs on the server, and once it has run, debug the recorded snapshot in Visual Studio Code. For a delegated admin to create and download a snapshot file that exists on the server on behalf of an end-user, the delegated admin must be part of the D365 Snapshot Debug permission group.