Business Central technical consultant for code, data and integrations

What a Business Central technical consultant is responsible for

The technical role covers all we build or move, not configure. That means extensions written in AL and custom API pages. It means report and document layouts with logic behind them. It also means links to other systems and scripts that convert old data. The role also covers the environments: sandboxes, production, app deployment and update scheduling.

A good technical consultant also says no. Before we write code, we check if a standard feature, a setting or a marketplace app already does the job. Custom code is a promise. Someone must carry it through every future update. So we keep it small, well named and documented.

Business Central technical consultant extension work, done the supported way

You customize Business Central through extensions that sit beside the base application. Table extensions add fields. Page extensions change screens. Event subscribers run your logic when standard code raises an event. Nobody edits Microsoft's code. That is why a tenant can take platform updates without a rewrite.

We develop against a sandbox or a container. Automated tests cover posting logic. Every object lives in a Git repository that you own. Each extension carries its own upgrade code. So data in custom fields survives a version change. We also switch telemetry on, so errors surface before users report them.

Integrations, APIs and data movement

Most technical requests involve another system, such as a web store, a warehouse provider, a payroll service or a customer portal. Business Central offers REST APIs, secured through Microsoft Entra ID. Where the standard endpoints lack a field, we publish a custom API page. Webhooks and business events let outside systems react to changes.

Data migration is the other half. First, we extract from the old system. Then we clean and map the records. Next, we load them through configuration packages, the cloud migration tool or purpose built import code. The choice depends on size and source. We rehearse every load in a sandbox. We also reconcile it against the legacy totals before cutover.

How a Business Central technical consultant handles environments and releases

The admin center is where you create, copy and restore production and sandbox environments. It is also where you schedule updates. We set up a sensible layout. It is usually one production environment plus sandboxes for testing and development. We also define how an extension moves from one to the next. So untested code never lands in live.

When pages are slow or a job queue entry keeps failing, we read the telemetry in Application Insights. We do not guess. Slow queries, lock timeouts and heavy reports show up there, with the object behind them. Fixes usually mean better filtering, a missing key, or moving work into a background task.

How to engage a Business Central technical consultant from our team

You can bring us a single task, such as one integration or one broken extension. Or you can add a consultant to a longer project beside your own staff or another partner. We begin with a short technical discovery. It covers current extensions, integrations, environment layout and known problems. That gives us a written scope before any build starts.

Two pitfalls come up again and again. One is inherited code with no source files. We recover and document it where we can. The other is technical work that starts before the functional design is settled. That leads to rework. So we ask for the process decision first. Then we build exactly that.

Business Central technical consultant FAQ

What language is Business Central customized in?

You extend Business Central in AL. It is a language built for the product. You write it in Visual Studio Code with the AL Language extension. We package the code as an app file. Then we install it in an environment, apart from Microsoft's base application.

Can you take over extensions written by another developer?

Yes. We ask for the source code and any documentation. We read what the extension does. Then we run it in a sandbox and note the risks we find. If the source is missing, we tell you plainly what we can and cannot recover.

Who owns the code you write?

You do. The AL source lives in a repository under your control. We hand over the app files, the build steps and the design notes. So another developer could continue the work without depending on us.

Do old C/AL customizations carry over for a Business Central technical consultant?

Not directly. Teams must reassess modifications made inside older NAV code. Then they rebuild them as AL extensions. Many turn out to be covered by standard features today. So the first step is deciding which customizations are still worth keeping.

Do we need a Business Central technical consultant if we stay standard?

Often only for a short time. A standard implementation still needs data loaded, environments set up and perhaps one integration. After that, functional support is usually enough. You then bring in a Business Central technical consultant when a new interface or report needs one.

Technical services in more detail

Each technical area has its own page with more depth. Pick the one closest to your task. Or use the contact page to describe the problem. We will then point you to the right Business Central technical consultant. For the product detail, see Microsoft Learn: development in AL for Business Central.