With each update of Dynamics 365 Business Central, Microsoft enhances what is often referred to as the base application and enhances the development environment. Dynamics 365 Business Central 2022 Wave 1 has several exciting new features in the development environment. One of the exciting features is the In-Client Performance Profiler
In 2021 release wave 2, Microsoft 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 and help troubleshoot performance issues in AL code in customer environments.
In 2022 release wave 1, Microsoft takes the performance profiler even further. The in-client performance profiler is a new app page reached on its own or from the Help & Support page.
One note is that it is only possible to capture the current session for the user who starts the profiler in this release wave.
The In-client performance profiler is accessible from the Help and Support Page or by searching for Performance Profiler in the Tell Me feature of Business Central.
This tool makes it easy for consultants and customer administrators to perform initial performance investigations without involving pro developers seamlessly.
Once the In-Client Performance Profiler page is open, click the start action, and perform the operation you’d like to profile from the user session. Once the process completes, use the stop action to end profiling and display the profiler results.
The profiler will display the call tree and the amount of time consumed by each app and process within the call tree. The profiler data is precious information when determining where there may be a performance issue.
Repeatability is important! Right alongside that, in my opinion, is efficiency. A recent task required me to set up several Application Services setups, including setting the log on account and password. I could have done all of these manually; however, I found it more efficient and repeatable to set up a script to handle the setup.
purpose was to review events and troubleshoot issues when processing these events. The files are saved in a folder structure divided and grouped by Year, Month, and Event Type. The grouping is helpful for troubleshooting and finding specific transactions, but with several types of events and, at times, a decent volume, there can be a decent amount of disk space wasted; realistically, there isn’t a need to keep diagnostic logs forever. The data does become stale after a certain period.

available.
integration scenarios or troubleshoot the reports during development.


There is the SP-SCM1009 Airpot which is a product with a bill of material (BOM), a subassembly, and Routing. The SP-SCM1009 Airpot demonstrates the standard production flow. The SP-SCM1011 Airpot Duo requires item tracking and uses components that also need item tracking. Another item, SP-SCM1004 Autodrip, has been set up to demonstrate various flushing methods for components and operations using Standard Cost. Item SP-SCM1008 Autodrip Lite has been added to the Item List to show the use variants.
the popularity, leaving many “bad actors” who try to compromise 
