Establishing a connection with BC

This completes the loop. The FastTrack wizard connected Business Central to Dime.Scheduler; this connector entry is the reverse path - it's what lets Dime.Scheduler write appointments back into BC. You give it two things: where to reach BC (the web service URL) and how to authenticate.

Open the connector setup

Production · Sandbox

tip

This page only covers the BC-specific bits. For everything else about connectors, see the connector setup docs.

Web service URL

The Dime.Scheduler extension in BC exposes two kinds of web service. Pick one in the connector's API Type field, then grab the matching URL for the Web Service URL field.

SOAP

In BC, open the Web Services page, find the Dime.Scheduler Appointment Card page, and copy its SOAP URL. It looks like:

https://{YOUR_URL_TO_BC}:7047/WS/Page/Appointment

API page (REST)

The REST URL follows this format:

https://{YOUR_URL_TO_BC}/api/dimeSoftware/dimeScheduler/v1.0/companies({COMPANY_ID})/appointments

Replace the URL to BC and the company ID (the company GUID):

Paste the finished URL into a browser to test it. For BC Cloud, the shape is:

https://api.businesscentral.dynamics.com/v2.0/{USER_DOMAIN_NAME}/{ENVIRONMENT_NAME}/api/dimeSoftware/dimeScheduler/v1.0/companies({COMPANY_ID})/appointments

Here, {USER_DOMAIN_NAME} is the Entra ID tenant GUID, {ENVIRONMENT_NAME} is the environment's display name, and {COMPANY_ID} is the company GUID from above.

Authentication

Which method?

For on-premises BC you have three options:

Method	SOAP Web Services	API page
Basic authentication	✅	✅
Windows auth: NTLM and Kerberos	✅	❌
OAuth2	✅	✅

Microsoft has deprecated everything except OAuth2, and the REST API page doesn't support Windows auth at all - so OAuth2 is the safe choice unless you have a specific reason otherwise. For BC online (Cloud), OAuth2 is the only option.

Basic / Windows (on-premises)

These two configure the same way: in the connector's Authentication section, pick the type and enter the credentials of a BC service account Dime.Scheduler can use.

OAuth2 with Microsoft Entra ID

OAuth2 takes a few steps because it relies on an app registration in Microsoft Entra ID. There are three:

1. Register an app in Entra ID for authenticating against Business Central.
2. Grant that app access inside Business Central.
3. Point the Dime.Scheduler connector at it.

Official docs

Microsoft's register-an-app guide covers the Entra ID side in depth.

Try it first

We have a walkthrough for setting up OAuth2 between Dime.Scheduler and BC on-premises via Docker - a safe way to rehearse before touching your test or production environment.

Step 1: Register the app [Microsoft Entra ID]

1. Sign in to the Azure portal.

2. Register an application in your Entra ID tenant:

   • Give it a name, e.g. Dime.Scheduler for Business Central.
   • Select the supported account type.

3. Add these Application API permissions:

   • Dynamics 365 Business Central: app_access
   • Dynamics 365 Business Central: API.ReadWrite.All

4. Grant admin consent. The result should look like this:

   

Step 2: Register the app in BC [Business Central]

You'll need the app's application (client) ID, directory (tenant) ID, and a client secret.

1. Search for Microsoft Entra Applications (or Azure AD applications on older versions) and open it.
2. Create a new application:
   • Paste the client ID into the Client ID field.
   • Add a description, e.g. Dime.Scheduler.
3. Assign permission sets to the company you're connecting:
   • D365 Basic ISV
   • Dime.Scheduler
   • plus any set needed to reach your custom objects

Step 3: Configure the connector [Dime.Scheduler]

First, create the client secret: in the Entra ID app, go to Certificates & secrets, click New client secret, and copy the value.

Then create the connector in Dime.Scheduler and fill in the Authentication section:

• Authentication type: MS Entra ID
• Tenant ID: the app's Directory (tenant) ID
• Client ID: the app's client ID
• Client Secret: the secret you just copied

Save it, and the OAuth2 connector is live.

Source App

The source app must match the value you set in the FastTrack Wizard back in Business Central - it's what tells Dime.Scheduler which back-office system a given resource, task or appointment belongs to.