When developing extensions for Dynamics 365 Business Central, an important architectural aspect when planning for a solution is the extension's dependency.
Imagine you have developed and published extension A into your Dynamics 365 Business Central. Extension A adds new tables and pages and extends standard tables and pages. Now you need to create extension B (to handle another set of isolated functionalities), and extension B must interact with tables and fields added from extension A.
If you start developing extension B and try to reference a table defined in extension A, you will receive an error (table is missing because you don't have the symbols from extension A).
Extension B can see entities defined in extension A only if it declares that it depends on extension A.
To see this concept in action, let's create a very simple extension (new project with Visual Studio Code and AL:Go!) for adding a new action button to the Customer Category List page.
The core part here...