Book Image

Mastering Microsoft Dynamics 365 Business Central - Second Edition

By : Stefano Demiliani, Duilio Tacconi
5 (3)
Book Image

Mastering Microsoft Dynamics 365 Business Central - Second Edition

5 (3)
By: Stefano Demiliani, Duilio Tacconi

Overview of this book

This book dives straight into guiding you through the process of building real-world solutions with the AL language and Visual Studio Code. It emphasizes best practices and extensibility patterns to ensure your extensions are well-structured, maintainable, and meet the needs of modern businesses. You'll learn advanced AL techniques, report creation methods, debugging strategies, and how to leverage telemetries for monitoring. Additionally, it covers performance optimization practices and API integration to help you create efficient and interconnected solutions. With a focus on extension development, this new edition allows you to jump right into coding without spending time on setup processes. This book introduces new chapters covering essential tasks that Business Central developers frequently encounter, such as file handling and printing management. Finally, the book expands its scope by including chapters on various integration aspects, including VS Code extensions, GitHub DevOps, Azure services, and Power Platform integrations. We’ll wrap up by covering Copilot capabilities in Business Central and how you can create your own generative AI copilots. By mastering these concepts and techniques, you'll be well-equipped to create powerful and customized solutions that extend the capabilities of Dynamics 365 Business Central.
Table of Contents (21 chapters)
19
Other Books You May Enjoy
20
Index

Snapshot debugging

As of the time of writing, none of the aforementioned debugging actions can be performed against an online production environment for security reasons. The only way to debug a production environment in the cloud is asynchronously by collecting a snapshot of the server-side code execution and analyzing it offline in Visual Studio Code. It is possible to collect any number of snapshots and apply specific breakpoints to them, called snappoints, that are not meant to stop the execution of the code at runtime but instruct the server to log and collect the call stack and state of the variables at the snappoint (or when the application goes into error).

To be able to create and/or collect snapshot debugger files, the user must be part of the D365 SNAPSHOT DEBUG standard permission set. This will provide the needed permission to the relevant objects involved in the snapshot debugging process, such as the Published Application system table.

We also need to declare...