Skip to main content

Microsoft Dynamics 365 Business Central Connector

Business Central holds the work and the resources. Dime.Scheduler holds the plan. Connecting the two is the moment those two pictures stop being separate: jobs, tasks and resources from BC become plannable things inside Dime.Scheduler, and the planning you do there flows back so dispatchers, accountants and the resources themselves all see one consistent reality.

Because both sides need to push information to each other, the integration runs as two independent channels, one in each direction. You set each one up once and the loop closes.

Business CentralDynamics 365
extension
Dime.SchedulerPlanning board
SetupStep 1 of 4

Install the extension

Install the Dime.Scheduler extension in Business Central - from AppSource for cloud, or the extension package on-premises.

The three required steps​

A working two-way integration takes three moves:

  1. Install the extension in Business Central. This is the codeunit and pages that know how to speak Dime.Scheduler's language - without it, BC has nothing to say. How
  2. Connect BC → Dime.Scheduler with the FastTrack Wizard. You point BC at a Dime.Scheduler tenant, authenticate, and pick which modules (jobs, service, assembly, manufacturing, ...) should travel. How
  3. Connect Dime.Scheduler → BC by adding a connector that knows where to reach this BC instance and how to authenticate against it. This is what lets the planning come back. How

What real deployments add​

A trial works with the three steps above. Anything you intend to run on real data goes on to tune how the connector behaves, which is what the configuration section covers: safeguards against deleting planned work, a scheduled job that keeps master data fresh, and an outbound queue that logs and optionally buffers everything BC sends. None of it is required to get running, and all of it is off by default.

Beyond the connector itself, budget for permission tuning so the service accounts on either side have exactly the access they need, and no more.

Check this first

The connector works on every supported BC version, but specifics differ between waves. Confirm yours against the requirements before you start - anything version-specific is flagged inline.