In-client performance profiler
Important
This content is archived and is not being updated. For the latest documentation, go to What's new and planned for Dynamics 365 Business Central. For the latest release plans, go to Dynamics 365 and Microsoft Power Platform release plans.
| Enabled for | Public preview | General availability |
|---|---|---|
| Users, automatically | 
Mar 1, 2022 |
Apr 1, 2022 |
Business value
In 2022 release wave 1, we add new capabilities to the AL performance profiler. In this release wave, we are going to empower functional developers/consultants, as well as customer administrators and power users to capture a user flow from within the web client, and view high-level information about time spent in the web client. This way, people can investigate which involved extensions consume the most time, including top-consuming method calls, for example.
Feature details
In 2021 release wave 2, we added the AL performance profiler to the Visual Studio Code AL experience. The performance profiler has empowered pro developers to investigate performance as part of developing new functionality, as well as help troubleshoot performance issues in AL code in customer environments, even in production.
In 2022 release wave 1, we are going to take this even further. Having this tool will make it easy for consultants and customer administrators to seamlessly perform initial performance investigations without involving pro developers, to be able to pinpoint performance issues and file support cases to the most likely owners of the app, be that a per-tenant extension, an AppSource app, or the Dynamics 365 Business Central core app. It will also be possible to share the resulting capture, making it faster for a pro developer to do further analysis without having to perform a repro of the issue locally.
The in-client performance profiler will be a new app page that can be reached on its own or from the Help & Support page. It can be opened in another browser window side-by-side with the user experience that you want to profile so that you can make sure the capture is as concise as possible and only contains the relevant steps. The page will contain actions to start and stop the capture of a user flow. You will be able to see the performance results of a capture, including time spent per involved extension, top method calls, and other metrics. You’ll also be able to download the capture so that you can share it with technical support or a pro developer, for example, for viewing in the Visual Studio Code AL profiler. Note that when exporting such profile captures, you should comply with local privacy laws, such as the General Data Protection Regulation.
In this release wave, it will only be possible to capture the current session for the user who starts the profiler.