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:

On Directions EMEA in Milan I delivered session about Architecture of PTE for Business Central. I was trying to find some rules when or why you should or shouldn’t split your PTE into multiple apps. Now I will try to catch this into this article.