Skip to main content
Cookbook · Business Central

Connect Business Central

Admin ~30 min

The most common integration. You'll install the BC extension, point it at your Dime.Scheduler instance, and confirm the first sync lands.

Before you start​

Check your BC version against the requirements first. The connectorConnectorAn integration that links Dime.Scheduler to a back-office system, routing data in and scheduling decisions back out. works on every supported version, but the specifics differ between waves, and finding that out halfway through the wizard is a poor use of an afternoon.

The mental model that makes the rest straightforward: the integration is two independent channels, one in each direction. BC pushes jobsJobA high-level container, comparable to a project, that bundles related tasks together with common information such as customer, billing, and address., tasksTaskA unit of work that belongs to a job. It appears in the open task list until it is scheduled to a resource., and resourcesResourceAn entity that can carry out work - a person, vehicle, tool, or room - that you schedule on the planning board. into Dime.Scheduler. Dime.Scheduler pushes planning back into BC. You configure each one separately, and the loop only closes when both exist. A setup where data arrives but planning never returns almost always means the second channel was never built.

1. Install the extension in Business Central​

The extension is the codeunit and pages that know how to speak Dime.Scheduler's language. Without it BC has nothing to say.

See the BC integration overview for what the connector adds to your environment.

2. Connect BC to Dime.Scheduler​

Run the FastTrack WizardFastTrack wizardThe setup wizard inside Business Central or NAV that connects it to Dime.Scheduler and switches on the modules to plan from. It writes the source app and creates the source types for each enabled module. in BC. You point it at a Dime.Scheduler tenant, authenticate, and choose which modulesFastTrack solutionOne module of the Business Central or NAV connector that makes a kind of record plannable, such as service orders or production routing. Each has its own enable switch in the FastTrack wizard. travel: jobs, service, assembly, manufacturing, and the rest.

Two fields on the wizard deserve a second look before you click Next. The environment is Dime.Scheduler's, not BC's: a sandbox BC company talking to production Dime.Scheduler is common and correct, but the reverse mistake pushes test data into a live tenant. And the seed a connector entry box, ticked by default, pre-creates the return-path connector for step 3, so leave it on.

Be deliberate about the module selection. Every module you enable is master data that starts flowing and needs to be right. Turning on everything "to see what happens" produces a noisy first sync that is harder to diagnose than a narrow one.

See connecting BC to Dime.Scheduler.

3. Connect Dime.Scheduler back to BC​

Add a connector in Dime.Scheduler that knows where to reach this BC instance and how to authenticate against it. This is the return path, and it is what makes the planning show up in BC. If the wizard seeded the entry, it is already waiting on the connectors page, wired to the right source app and environment, and only needs its web service URL and credentials.

The field that ties the two channels together is the source app. It must match the code the wizard set in BC; if it does not, each channel works in isolation and the loop never closes.

See connecting Dime.Scheduler to BC for the web service URL and authentication options.

4. Verify the first sync​

Go to transactions and confirm data actually arrived. Then plan something in Dime.Scheduler and confirm it lands in BC, because that exercises the second channel, which the first check does not.

If anything failed, the errors page lists every faulted appointmentAppointmentA task scheduled to a resource for a specific period - the scheduled instance you see on the planning board., split into Dynamics, Exchange, and Webhook tabs so you can work one integration at a time.

What real deployments add next​

The three steps above give you a working trial. Anything running on real data goes on to tune behavior, and all of it is off by default:

  • Safeguards against deleting work that has already been planned.
  • A scheduled jobJob queueBusiness Central’s scheduler for background work. The connector relies on job queue entries to process the outbound queue and to synchronize master data without blocking users. that keeps master data fresh.
  • An outbound queueOutbound queueThe Business Central table where records headed for Dime.Scheduler wait when asynchronous processing is on. A job queue entry dispatches them a few minutes later and retries failures. that logs and optionally buffers everything BC sends, which is worth having before you need it.

See configuring the connector. Budget time for permission tuning as well, so the service accounts on both sides have exactly the access they need and no more.

Last updated on by Hendrik Bulens