Skip to main content

Troubleshooting

The most common questions about the two-way message flow between Dime.Scheduler and Business Central, grouped by what you're seeing.

Find your symptom

Appointments don't show up in Business Central
Usually a missing or invalid connector, or BC is unreachable from Dime.Scheduler.
Appointment in BC is stuck on "Error"
Dime.Scheduler delivered it, but BC couldn't process it. Check the Dime.Scheduler Appointments table in BC.
Request channel timed out
Firewall is blocking traffic from Dime.Scheduler to BC, or the request is too slow.
HTTP Request Unauthorized
Wrong credentials, expired secret, or missing API permissions on the BC side.
BC complains about time synchronization
Server clocks are drifting. Token validation fails when clocks are off by more than a few minutes.

Business Central to Dime.Scheduler​

The first thing you do on a new Dime.Scheduler instance is run the FastTrack Wizard in Business Central. Work through every step carefully.

The first step is also the most common place to get stuck: it's where you set up the flow to Dime.Scheduler, with the environment and the credentials to authenticate against it.

Watch out for these:

  • User/password authentication
    • An account used in more than one tenant.
    • A real person's account instead of a service account. The day that person resets their password, the integration breaks. Use a service account like [email protected].
    • Don't use any domain managed by Dime Software, either: that's a security risk.
    • It must be a Forms account on a domain your customer controls. MS Entra ID accounts aren't supported by the API.
  • Environment (sandbox or production): the on-prem option refers to Dime.Scheduler on-prem, not BC on-prem.

Dime.Scheduler to Business Central​

The flow from BC to Dime.Scheduler is easy to set up, thanks to the FastTrack Wizard and the connector. The return flow is trickier, because it depends on how that particular BC is set up. Two things can fail: Dime.Scheduler can't reach BC, or BC receives the appointment but can't process it.

Appointments don't show up in Business Central​

Start at the transactions. Open them from the sidebar, or right-click the appointment on the planning board and choose View transactions.

That opens the appointment's detail page: basic info, the associated connector (if any), and every transaction that tried to write back to Business Central, Exchange, or a webhook.

API permissions

The transactions usually tell you exactly what went wrong. Common causes:

  • No connector for this item. Data sent from BC carries a Source App identifier. To send a planned appointment back, Dime.Scheduler looks for a connector with the same Source App. No match, nothing sent.
  • Invalid or incomplete connector. Usually the wrong URL or credentials (or app registration details, for BC cloud).
  • Back-office unavailable: the administrators need to make the BC SOAP URL reachable from Dime.Scheduler.

Appointments couldn't be processed in Business Central​

When Dime.Scheduler drops the appointment into BC, the transaction is marked successful on the Dime.Scheduler side. That doesn't guarantee BC processed it.

In Business Central, open the Dime.Scheduler Appointments table. It lists the transactions and their status. Anything not marked Processed went wrong: click the status column for details.

Appointment list

Processed means the planning data went through as expected. Error means it didn't, and the Error Message column tells you exactly why.

Time zone mismatch​

Appointments scheduled in Dime.Scheduler show incorrect times in Business Central (e.g. 9 AM in Dime.Scheduler appears as 7 AM in BC).

Applies to: Business Central SaaS.

Cause​

A time zone mismatch between Dime.Scheduler and Business Central, usually a fixed shift (2 hours is common), almost always from an incorrect time zone in the connector setup. There's no error code for this: the appointment is delivered fine, just at the wrong time, so it's a configuration quirk rather than an exception.

Fix​

Open the Dime.Scheduler Setup page in Business Central and set the Time Zone field:

Dime.Scheduler FastTrack Wizard - Time Zone Configuration

The same field also appears at the bottom of the FastTrack wizard:

Dime.Scheduler FastTrack Wizard - Time Zone Configuration

Transaction errors​

Every failed transaction is tagged with a stable code (e.g. [DSBC003]). See Transaction Errors for the full reference and partner-facing fixes.