Skip to main content


A single instance of Dime.Scheduler is able to connect with multiple back-office applications. A back-office application is an umbrella term for any system that can be used to provide data for planning. Many of these systems allow you to create multiple companies, business units, operational units, etc. Each of these organizational entities can be a data source for Dime.Scheduler.

In order to send data back from Dime.Scheduler to these source applications, connection info needs to be specified.

Source application

The concept of a source application is crucial in Dime.Scheduler, and it's worth revisiting its definition.

Since multiple back-office systems can connect to the same Dime.Scheduler instance, there arises a conflict regarding unique data records. To address this data integrity concern, we've introduced an additional dimension called the source application identifier. A source app serves as a unique identifier, indicating the origin of a record. When you make a task or resource available in Dime.Scheduler, we can identify the system from which that record originates. This information is essential for directing planned task data to the appropriate system whenever the schedule is modified by planners.

In essence, the source app acts as the link facilitating bi-directional communication between a back-office system and Dime.Scheduler. When utilizing the standard connectors provided by Dime Software, you'll be prompted to enter a source app value. This value is crucial because, when planning a task for this source application, Dime.Scheduler will activate all the connectors associated with that particular source app.


The following fields can be managed in the connections setup view:

Source ApplicationThe back-office application sends this code to establish itself as the source of a job and task, enabling Dime.Scheduler to decide where to transmit data back to the back-office application.

This code must be identical in both the back-office application and Dime.Scheduler. If the source app of the planned appointment doesn't have a match with any entries in the connector setup, Dime.Scheduler won't be able to send any data.
Send appointments to back officeSelect to send the appointment data to the back-office application.
Web ServiceThe URI that indicates the back-office application to connect to.
Back OfficeThe type of back-office application you are connecting with.
LoginThe credentials with which to connect to the back office's web service.
PasswordThe credentials with which to connect to the back office's web service.

One of the key takeaways of Dime.Scheduler is that the application has no specific knowledge of the back-office system. In fact, it is not even aware of its presence. Using a set of well-defined interfaces, systems are able to communicate with each other without knowing the actual implementation. There are the standard connectors for BC, NAV and Exchange, among a few others, built by Dime Software, but connectors should not be limited to what Dime Software builds as standard.

Back-office systems

WebhookA convenient tool to try out the webhook connector is
Power AutomateBy using the triggers in Dime.Scheduler's certified connector, the Power Platform will register a connector automatically in the setup. Hence, no action is required. It is important to not remove this connector, otherwise Dime.Scheduler won't be able to start the Power Automate flows.
Microsoft Dynamics NAVRead more here.
Microsoft Dynamics 365 Business CentralRead more here.