Book Image

Dynamics 365 Business Central Development Quick Start Guide

By : Stefano Demiliani, Duilio Tacconi
Book Image

Dynamics 365 Business Central Development Quick Start Guide

By: Stefano Demiliani, Duilio Tacconi

Overview of this book

Microsoft Dynamics 365 Business Central is the new SaaS ERP proposition from Microsoft. This latest version has many exciting features guaranteed to make your life easier. This book is an ideal guide to Dynamics 365 Business Central and will help you get started with implementing and designing solutions for real-world scenarios. This book will take you through the fundamental topics for implementing solutions based on Dynamics 365 Business Central (on-premise and SaaS). We'll see the core topics of the new development model (based on extensions) and we'll see how to create applications with the new Microsoft ERP proposition. The book begins by explaining the basics of Dynamics 365 Business Central and the Microsoft ERP proposition. We will then cover topics such as extensions, the new modern development model of Visual studio code, sandboxes, Docker, and many others. By the end of the book, you will have learned how to debug and compile extensions and to deploy them to the cloud and on-premise.You will also have learned how to create serverless business processes for Microsoft Dynamics 365 Business Central.
Table of Contents (13 chapters)
Title Page
Packt Upsell
Contributors
Preface
Index

Developing the extension


We've structured our project folder as follows:

We have an Src folder and under that we have a subfolder for every functionality and then for object type.

The name of each AL file is created using Microsoft's naming guidelines:

  • Each file name must start with the corresponding type and ID, followed by a dot for full objects or a dash for extensions:
    • Full objects: <Type><Id>.<ObjectName>.al, such as Tab.50100.MyTable.al
    • Extensions: <Type><BaseId>-Ext<ObjectId>.<ObjectName>.al : page 50100 MyPage extends Customer Card such as Pag21-Ext50100.MyPage.al
  • It is required to use a prefix or suffix for the name property of the fields in your extension. You would then use the Caption/CaptionML values for what to display to the user. This avoids the collision of fields between extensions:
    • A tag must be at least three characters
    • The object/field name must start or end with the tag
    • If a conflict arises, the one who registered the tag always wins...