Book Image

Programming Microsoft Dynamics 365 Business Central - Sixth Edition

By : Marije Brummel, David Studebaker, Christopher D. Studebaker
Book Image

Programming Microsoft Dynamics 365 Business Central - Sixth Edition

By: Marije Brummel, David Studebaker, Christopher D. Studebaker

Overview of this book

Microsoft Dynamics 365 Business Central is a full ERP business solution suite with a robust set of development tools to support customization and enhancement. These tools can be used to tailor Business Central's in-built applications to support complete management functions for finance, supply chain, manufacturing, and operations. Using a case study approach, this book will introduce you to Dynamics 365 Business Central and Visual Studio Code development tools to help you become a productive Business Central developer. You'll also learn how to evaluate a product's development capabilities and manage Business Central-based development and implementation. You'll explore application structure, the construction of and uses for each object type, and how it all fits together to build apps that meet special business requirements. By the end of this book, you'll understand how to design and develop high-quality software using the Visual Studio Code development environment, the AL language paired with the improved editor, patterns, and features.
Table of Contents (12 chapters)
9
Successful Conclusions

Secondary keys and SumIndexFields

The Playlist Line table's default primary key was Document No.. For the primary key to be unique for each record, another field is needed. For a Line table, the additional field is the Line No. field, which is incremented via AL code for each record. So, we'll change the key for table 50003 accordingly:

We know that a lot of reporting will be done based on the data in Radio Show Ledger. We also know that we want to do reporting on data by Radio Show and by the type of entry (individual song, specific advertisement, and so on). So, we will add secondary keys for each of those, including a Date field so that we can rapidly filter the data by Date. The reporting that is financial in nature will need totals of the Fee Amount field, so we'll put that in the SumIndexFields column for our new keys:

We know that to do the necessary listenership analysis, the listenership ledger needs an additional key, combined with SumIndexFields for...