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 connector 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 jobs, tasks, and resources 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 Wizard in BC. You point it at a Dime.Scheduler tenant, authenticate, and choose which modules travel: jobs, service, assembly, manufacturing, and the rest.

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.

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 appointment, 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 job that keeps master data fresh.
  • An outbound queue 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