TECHNICAL CONSULTANCY
TECHNICAL
CONSULTANCY.
ASSESS. DESIGN. CHALLENGE.
Technical consultancy is about making the right
decisions before they become expensive to change.
NAV. Business Central. Architecture. Integration.
Performance. Upgrades.
DISCOVERY
UNDERSTAND
THE SYSTEM.
Before changing a NAV or Business Central
environment, establish what is actually there.
ARCHITECTURE
DECIDE
WHERE IT BELONGS.
Not every requirement belongs in custom code.
Not every requirement belongs in standard
functionality either.
STANDARD
Use the platform where the platform already
provides the required behaviour.
EXTENSION
Isolate application changes through extensions,
events and controlled dependencies.
INTEGRATION
Keep external responsibilities outside the
application where they belong.
DATA
Define ownership, flow and lifecycle before
moving or duplicating data.
TECHNICAL DESIGN
TURN REQUIREMENTS
INTO DESIGN.
TABLES
Tables, table extensions, keys, fields,
relations and data ownership.
PAGES
Pages, page extensions, actions, navigation
and user interaction.
CODE
Codeunits, interfaces, events, subscribers,
posting logic and transaction boundaries.
REPORTING
Reports, queries, datasets and the appropriate
route for operational and analytical data.
SECURITY
Permissions, permission sets and separation
of responsibilities.
PROCESSING
Job queues, background processing, error
handling and controlled execution.
INTEGRATION & DATA
DEFINE
THE BOUNDARIES.
Integrations fail when ownership, validation
and failure handling are treated as secondary
details.
PERFORMANCE
FIND
THE REAL PROBLEM.
Performance problems are usually symptoms.
The useful question is what is causing them.
DATABASE
SQL execution, locking, indexes and database
access patterns in legacy NAV environments.
AL
Record access, loops, filtering, unnecessary
database calls and execution patterns.
DATA
FlowFields, calculated data, large datasets
and inefficient processing.
TRANSACTIONS
Lock duration, transaction scope and processes
that do more work than necessary.
TELEMETRY
Use available telemetry and performance data
instead of relying on assumptions.
ROOT CAUSE
Identify the technical cause before changing
infrastructure or rewriting code.
UPGRADE & DELIVERY
MOVE FORWARD
WITHOUT GUESSWORK.
TECHNICAL PARTNERSHIP
TECHNICAL
JUDGEMENT.
Good consultancy is not about producing more
documents.
It is about identifying the decisions that
matter.
Whether the question concerns an old NAV
implementation, a Business Central upgrade,
an integration, a performance problem or a
proposed customisation, the technical
consequences should be understood before
implementation begins.
Sometimes the correct answer is to build it.
Sometimes it is to use standard functionality.
Sometimes the architecture needs to change.
And sometimes the correct answer is simply
not to do it.