Architecture / Design : Expert peer recommendations

(0) Share

Report

Posted on by Community member

Hello BC Peer Experts,

Over the period our development team have customized NAV 16//18 to meet some of the features to support our business needs. Now, we are in process of migrating these features to BC cloud version. We are exploring couple of options and make sure our design and architecture is the best based on other factors considered. Question is should we build dedicated BC instance to meet our Operations needs or build this as extension and keep part of core finance module?

Our primary factors are:

• Make sure business users have best possible user experience with business processes//workflows relevant to specific teams.
• Make sure BC solution is segregated so in the future if we were able to build this functionality in other Ops systems we can disable//disconnect quickly without any complexities and dependencies.
• Solution is centralized, standardized, and expandable to other entities//regions for quick onboarding for new entities, easy integrations and minimal maintenance and support in the future for upgrades etc

Categories:

Dynamics 365 Business Central

All responses (2)

Answers (0)

Community member 2 on at

Like (0)

Report

Architecture / Design : Expert peer recommendations

Thank you, Manish.

One other factor is we have multiple localizations within organization, if we have single extension for whole solution won't that increase complexity when we need to deploy single extension to other entities with localization?
ManishS 6,578 on at

Like (1)

Report

Architecture / Design : Expert peer recommendations

My suggestion would be to go with single extension for better performance.
Do not build multiple extension which are dependent on each other, this will hamper performance & upgradation of each extension.

Do follow Universal Code Requirement as standard.

Try reusing your code, create small function to breakdown the checks & tests.