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

Handling the CI/CD pipeline

When you create a repository with AL-Go for GitHub, it automatically adds a CI/CD pipeline to it. I suggest protecting the main branch in the GitHub repository by always requiring a pull request before accepting code changes (and also setting the number of approvals for pull requests).

To do that, select your main branch, and under Protect matching branches set the Require approvals option accordingly:

Figure 15.15: Branch protection options

When using pull requests, developers will create a fork or a branch in which they will complete their work. When creating the pull request, their change will be merged with the main branch, and a CI/CD workflow will be run on the merged code before it is pushed into the repository.

If you commit a code modification via a pull request to the main branch, you will see that the CI/CD workflow starts:

Figure 15.16: CI/CD workflow in operation

This workflow performs the following steps:

...