Connectors

One Dime.Scheduler instance can connect to many back-office systems at once. A back-office system is any system that feeds Dime.Scheduler planning data: Business Central, NAV, a webhook target, and so on. Many of them host several companies or units, and each can be its own data source.

A connectorConnectorAn integration that links Dime.Scheduler to a back-office system, routing data in and scheduling decisions back out. entry represents one such endpoint and tells Dime.Scheduler how to write planning data back to it. Every connector has three groups of settings:

• Basic info
• Connector info
• Authentication info

Basic info

These fields are just for your own bookkeeping, to help you tell connected systems apart:

• Name
• Description

Connector info

This group identifies what kind of system you're connecting to.

Type

Supported back-office system types:

• Microsoft Dynamics 365 Business Central
• Microsoft Dynamics NAV
• Webhook

Enabled

When true, Dime.Scheduler writes planning data back to this system for every appointmentAppointmentA task scheduled to a resource for a specific period - the scheduled instance you see on the planning board. whose source typeSource typeAn identifier that, together with the source app, tells Dime.Scheduler which back-office table a record belongs to. matches the connector's. When false, the connector is ignored.

Web Service URI

The endpoint Dime.Scheduler posts data back to.

API Type

Some back-office types support more than one API type:

Back-office system	Supported types	Comment
Microsoft Dynamics 365 Business Central	SOAP web services API pages	Read more here.
Microsoft Dynamics NAV	SOAP web services	Read more here.
Webhook	REST

Bi-directional message flow

What you configure here only covers the flow from Dime.Scheduler to the back-office system. The opposite direction (getting data into Dime.Scheduler) is set up in that system itself.

These are the back-office types Dime Software manages and supports on the customer's behalf:

• Webhook
• Power Automate
• Microsoft Dynamics NAV
• Microsoft Dynamics 365 Business Central

See below for the supported data formats and authentication methods.

Source type

When several systems share one Dime.Scheduler instance, records could collide. The source application (source appSource appAn identifier Dime.Scheduler attaches to data so it can route a change back to the correct back-office system.) solves that: it's a unique identifier stamped on every record, marking where it came from. So when a planner changes the schedule, Dime.Scheduler knows exactly which system to send the change back to.

With the standard connectors you'll be asked for a source app value. Planning a taskTaskA unit of work that belongs to a job. It appears in the open task list until it is scheduled to a resource. for that source app fires every connector tied to it.

Run the simulation below: schedule a task on the board, then watch Dime.Scheduler match its source app to a connector and call the right back office.

Source app routing

Open tasks

Service order S-1042BC-USA

Service order S-2087BC-CANADA

Alice Martin · Mon

1Schedule

2Match source app

3Deliver

Drag a task onto Alice’s lane to schedule it. We take over from there.

Crud type

You can limit a connector to certain operations: create, update, or remove an appointment. For example, a separate connector with a single CRUD type could fire a different email through a Power Automate flow.

Authentication

Dime.Scheduler supports the authentication mechanisms back-office systems commonly require.

Basic authentication

Just a login and password.

Windows authentication (NTLM, Kerberos)

Just a login and password. Not supported by the REST API.

MS Entra ID

Needs three values:

• Tenant ID
• Client ID
• Client Secret

OAuth2

Any OAuth2-capable identity provider works here.

The client-credentials grant type is supported, in two flavours:

• Client secret basic: credentials go in the HTTP Basic Authentication header.
• Client secret post: credentials go in the request body.

Both need the same details:

• Authorization Server: the endpoint Dime.Scheduler calls first to exchange credentials for a token.
• Client ID: the app registration in the OAuth2 provider.
• Client Secret: that app's secret value.
• Scope: optional, space-delimited values Dime.Scheduler needs to post back to the web service URL.

Don't know which one to choose?

OAuth2 and MS Entra ID (which implements OAuth2) are the industry standard. Use them when you can; with OAuth2, client secret basic is the safer of the two flavours.

For quick tests, Basic Authentication is the fastest way to get going, and NTLM/Windows are fine when Windows AD is set up properly on the NAV/BC server. These are older methods the industry has moved away from, so reach for them only when OAuth2 or MS Entra ID isn't an option.

Supported authentication methods per standard connector:

Connector	Basic Auth	Windows Auth	NTLM	MS Entra ID	OAuth2: Basic Auth	OAuth2: Body Auth
NAV	✅	✅	✅	❌	❌	❌
Business Central on-prem	✅	✅	✅	✅	✅	✅
Business Central cloud	✅	❌	❌	✅	✅	✅
Webhook	✅	❌	❌	✅	✅	✅

Supported data formats:

Connector	SOAP	JSON
Business Central on-prem	✅	✅
Business Central cloud	✅	✅
NAV	✅	❌
Webhook	❌	✅

REST/JSON is preferred, as it's the industry default.

Backoffice-specific connector setup

For the system-specific details:

• Business Central
• NAV
• Power Automate
• Webhook