Book Image

Mastering Microsoft Dynamics 365 Business Central

By : Stefano Demiliani, Duilio Tacconi
Book Image

Mastering Microsoft Dynamics 365 Business Central

By: Stefano Demiliani, Duilio Tacconi

Overview of this book

Dynamics 365 Business Central is an all-in-one business management solution, which is easy to adopt and helps you make smarter business decisions. This book is a comprehensive guide to developing solutions with Microsoft ERP (in the cloud and also on-premises). It covers all aspects of developing extensions, right from preparing a sandbox environment to deploying a complete solution. The book starts by introducing you to the Dynamics 365 Business Central platform and the new Modern Development Environment. You'll then explore the sandbox concept, and see how to create sandboxes for development. As you advance, you’ll be able to build a complete advanced solution for Dynamics 365 Business Central with AL language and Visual Studio Code. You'll then learn how to debug and deploy the extension and write automatic testing. The book will also take you through advanced topics like integration (with Azure Functions, web services, and APIs), DevOps and CI/CD techniques, and machine learning. You'll discover how Dynamics 365 Business Central can be used with Office 365 apps. Finally, you'll analyze different ways to move existing solutions to the new development model based on extensions. By the end of this book, you'll be able to develop highly customized solutions that meet the requirements of modern businesses using Dynamics 365 Business Central.
Table of Contents (25 chapters)
Free Chapter
1
Section 1: Dynamics 365 Business Central - Platform Overview and the Basics of Modern Development
5
Section 2: Developing Extensions for Dynamics 365 Business Central
10
Section 3: Debugging, Testing, and Release Management (DevOps)
15
Section 4: Advanced Integrations with Dynamics 365 Business Central
20
Section 5: Moving Solutions to the New Extension Model

Branching policies

To maintain the quality of your app, you can define policies that must be met before changes from the developer can be integrated into the selected branch.

Mostly, the policy is defined on the master branch, but it could be any branch you want to keep healthy. If you define the policy for a branch, changes cannot be pushed into this branch directly, but only through Pull Requests (PRs). See the Pull request section for more details. In this way, each change is checked and tested, and if the policy is not met, the change will not make it into the branch. You can define the following in the policy:

  • The minimum number of reviewers: This is how many reviewers must approve the PR to be accepted.
  • Check for linked work items: This forces developers to associate the PR with work items to have links between requirements and changes.
  • Check for comment resolution...