Today I was helping a partner on discovering performance issues on its Dynamics 365 Business Central online tenant. When analyzing the telemetry data with Application Insights, we discovered a lot of Long Running Query signals (event id RT0005) linked to the OnCompanyOpen trigger. So strange… until analyzing its installed per-tenant extensions, we discovered an extension with a code like the following: This extension subscribes the OnCompanyOpen trigger and then adds a custom code for logging stuffs related to the user on custom tables. Please don’t do in this way if you need that…

Starting from Dynamics 365 Business Central 2020 Wave 2 (v17) administrators can define retention policies for tables to specify how frequently they want Business Central to delete outdated data in tables that contain log entries and archived records (they are essentially a way to define when data on certain tables expires in your database). Why you should use retention policies with Dynamics 365 Business Central? Essentially for the following reasons: reduce the size of your database reduce the impact on performances due to a large database delete logs and archives tables that are normally…

Talking in these days with some partners, I discovered that it’s not so clear how to handle the possibility to install apps on a Dynamics 365 Business Central SaaS tenant. Who can do that? The answer is: it depends As a general rule: To install extensions from AppSource or add per-tenant extensions to a tenant, you must have the right permissions and more specifically you must either be a member of the D365 EXTENSION MGMT user group or you must have the D365 EXTENSION MGMT permission set . If you are an administrator (SUPER role), you can assign user groups and permissions to other users…

One of the top requested features for Dynamics 365 Business Central from a long time is absolutely one: debugging the production environment ! And now you can Dynamics 365 Business Central version 17 introduces a feature called Snapshot Debugging . Snapshot Debugging allows a delegated admin to record AL code that runs on the server side and then debug the recorded  snapshot  in Visual Studio Code in an offline manner. How does this feature work? Imagine that I have deployed an extension to my online customer and this extension throws an error on code. I want to debug the cause…