Breaking up BaseApp | Business Central

Social media is fantastic and it can be used in many different ways. Where most people are mostly consumers others use it to ask questions. Some share knowledge and experience and gain loyal followers. This is pure awesomeness and mostly rewarded with the Microsoft MVP award for those who don’t give up.

Drive Change

Very few succeed in using social media to drive change. Those who do are known by many such as Elon Musk and Greta Thunberg.

Pages: 1 2

8 responses to “Breaking up BaseApp | Business Central”

  1. Concerning the integration of Fixed Assets into Purchase and Sales, the question about extending option fields naturally arises. May be there should be fix ranges of option values like 0 to 100 for Base App, 1000 to 9999 for certified apps and 10000 to … for per tenant customizations. In that context it would of course be necessary to extend table relations depending on option values, too. May be there should be separate OnValidate triggers for each option value, too (but this would mean the possibility of extending triggers…)

    Like

  2. I would by interested too.

    The first thing i would do, is doing a ruthless cleanup of the base- app.
    There are so many functionalities, which are three or more times in the solution, everyone with another bug.
    I think this would reduce the base app by 10% or more.

    Then i would change to a more usefull (object)- model that reduces this “functionality” above, by putting the function where it is used (Like SalesHeader.Post(Ship,Invoice,”Posting Date”,”Document Date”), which may call CU80 in background, but the entry point should be in SalesHeader).
    This would also allow an easier extendability, because we do not need a seprate event for every function that implements the same functionality.
    After this is done, my next step would be creating a more layered model (similar to the OSI-Model). (the system app is a start of this)

    But first of all we need a TESTED solution that allows concurrent apps accessing/extending the same global data, like extending SalesLine.Type or changing OnValidates, OnLookups which is required from some addons and their business cases.
    And if there is not a solution for that, the whole project is dead, because in my opinion, we haven’t seen the heavy addons here. So we did not see the real problems.

    Like

Leave a reply to Breaking up BaseApp | Business Central – 365 Community Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.