If you are reading this, may be you are one of the growing number of partners and developers who started to develop extensions for Microsoft Dynamics 365 Business Central. And may be you started thanks to the AI tools which are making the development much easier than it was before. But AI is not solving everything. It can write the code for you, but it will not tell you how to architect your solution, how to deliver it to customer, how to maintain it. And these are the things which are making…

See previous part first - SaLi architecture for Microsoft Dynamics 365 Business Central, part 1

If you are developing solutions for Microsoft Dynamics 365 Business Central and you are building them from multiple applications (see Split or not to split), may be you are now experiencing some problems with the dependencies between your apps, chaos made by development withouth rules. We were there too and this is example of dependency chart of one our solution:

Since we started to use VSCode for AL development, I hear discussions that writing UI texts like ToolTips etc. should be done by someone else than developer. And I must agree. We - developers - are lazy kind and writing text is not our popular game. We are able to write some generic text, mostly automagically generated by different tools we are using to write code, but such a text is mostly equal to 0 Shannons (no, I am not talking about @Shannon Mullins). But how to solve this?