Skip to main content

Configuring the connector

Installation answers which Dime.Scheduler this Business Central talks to. Modules answer what travels between them: jobsJobA high-level container, comparable to a project, that bundles related tasks together with common information such as customer, billing, and address., service ordersService orderA Business Central service management document. The service order solution plans it as one task or as one task per service item line, and writes the assignment back as a resource allocation., 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 connectorConnectorAn integration that links Dime.Scheduler to a back-office system, routing data in and scheduling decisions back out. moves, and none of them are required to get a connection running. 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. 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 appointmentAppointmentA task scheduled to a resource for a specific period - the scheduled instance you see on the planning board. arrives from Dime.Scheduler that BC cannot process because a resourceResourceAn entity that can carry out work - a person, vehicle, tool, or room - that you schedule on the planning board. is missing a unit of measure.

Left alone, both situations fail quietly. Two switches on the Dime.Scheduler SetupDS SetupThe connector’s setup page in the back office (DS Setup in NAV, DS Connector Setup in Business Central). It holds the same settings as the FastTrack wizard, plus actions to send data manually. 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 categoryCategoryA visual indicator (a color) applied to appointments to classify or label them. 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 queueJob 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.. 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.