I think that everyone of you already knows that when working with Dynamics 365 Business Central, table extensions are killers for performances. But how much? That’s a question that I’ve also done to myself a lot of time when working with partners or when creating my own solutions. Is there a “deadline” for how many table extensions can I create for the same table in order to not kill my performances? In these days I was working on preparing a webcast for Microsoft WE (scheduled for late January) and for this webcast I’ve decided to create a small test myself to “mesasure” the impact…

Telemetry, telemetry, telemetry… this is an hot topic in your developer’s and admin’s life in the cloud. We have talked a lot about using Application Insights for handling the telemetry data of your Dynamics 365 Business Central tenant running in the cloud and in the last events Microsoft, me and others (like my friend Duilio) explained how to use some important tools for querying your telemetry data, like: Log Analytics and KQL queries directly from the Azure Portal Jupyter Notebooks with Azure Data Studio and KQL queries directly from your desktop Power BI reports (see some samples here…

Do you remember this slide? This was (and is) one of my most shared slides ever (from me, from third-party partners and also from Microsoft’s PTS team). This explained common problems on using per-tenant extensions on a SaaS environment: Now things are changed and this slide must be updated (it’s overdue) Starting from Dynamics 365 Business Central version 17, per-tenant extensions (PTE) are now tenant-isolated . In version 17, two PTEs with the same Id deployed to different tenants will no longer be in conflict. This means that you can install a PTE with the same Id and version…

In a demo at the Microsoft’s Reactor event in October I talked about the performance advantages on moving Azure Functions from Consumption to Premium plans when needed on certain scenarios. When you create a function app in Azure, you must choose a hosting plan for your app. There are three basic hosting plans available for Azure Functions:  Consumption plan Premium plan Dedicated (App Service) plan (not mentioned in this post). The Azure Functions Premium plan (sometimes referred to as Elastic Premium plan) provides features like VNet connectivity, no cold start, and premium hardware…