Skip to main content

Configuring the connector

Installation answers which Dime.Scheduler this Business Central talks to. Modules answer what travels between them: jobs, service orders, production, and the rest. This section answers a third question that sits underneath both: how the connector behaves while it does that work.

These settings are global. They do not belong to any one module, they apply to every piece of data the connector moves, and none of them are required to get a connection running. The FastTrack Wizard deliberately leaves them alone so that a first setup stays short. For anything running on real data, they are where you tune the integration to fit how your organization actually works.

There are three decisions to make, and they are independent of one another.

What happens when things go wrong​

The connector moves data between two systems that each have their own rules, and sometimes those rules disagree: an order is deleted in BC while planning still exists for it in Dime.Scheduler, or an appointment arrives from Dime.Scheduler that BC cannot process because a resource is missing a unit of measure.

Left alone, both situations fail quietly. Two switches on the Dime.Scheduler Setup page change that: one blocks deletions that would destroy planning, the other pushes BC's processing errors back to Dime.Scheduler so planners see them where they are already working. Both are covered in safeguards and notifications.

Keeping master data fresh​

The wizard pushes master data across once. After that, every resource you add, filter you rename, or category you retire in BC is invisible to Dime.Scheduler until something re-publishes it. On a real deployment that drift shows up as ghost resources and filters that no longer match.

A small codeunit re-publishes the same master data on a cadence, which you schedule through BC's job queue. Master data synchronization explains how to set it up and how often to run it.

How outbound calls are sent​

By default, every change a user makes in BC opens an HTTP call to Dime.Scheduler and waits for it to return before the user's action completes. That is simple, but it ties a click to a network round trip and loses the call outright if Dime.Scheduler is briefly unreachable.

The outbound queue lets you log every call for auditing, and optionally buffer those calls for background processing with automatic retries.