Skip to main content
Cookbook

Recipes for common goals

The rest of the docs explain features and concepts. This page works the other way around: pick a goal, follow the steps. Each scenario stitches together the pages you'd otherwise have to hunt down yourself.

Setup & access

Get people into Dime.Scheduler with the right access and the right tools.

Admin ~10 min
Onboard a new planner
Create the user, give them access, and set them up with a workable layout on first login.
Admin ~15 min
Roll out the mobile app to field workers
Provision the resource, create the matching user, and walk them through installation and sign-in.
Admin ~15 min
Lock down with data-driven security
Restrict what each planner can see based on the data, not just the role.

Personalization

Almost everything in Dime.Scheduler is configurable - workspaces, colors, fields, actions. Make it fit how your team actually works.

Planner ~20 min
Build a personal workspace
Arrange components, pick layouts, and save it as a profile that you (or a whole user group) can reuse.
Admin ~10 min
Color-code the planning board with indicators
Define categories and time markers so a property - status, priority, customer type - is visible on the board at a glance.
Admin ~10 min
Generate appointment subjects with field templates
Drive subject and body content from job/task fields instead of relying on what the back-office sends.
Admin ~20 min
Extend the appointment card with templates
Add custom fields to the appointment card so planners can capture data beyond the defaults - and push it back to the back-office.
Developer ~15 min
Add a deep-link action to the planning board
Wire a custom URL action so planners can jump to an external system from a context menu.

Planning workflows

Day-to-day planner work, from quick drag-and-drop scheduling to long-term project planning.

Planner ~5 min
Ad-hoc service planning with drag and drop
Pull open tasks onto the planning board to schedule them - fast and reactive, ideal for service and professional services teams.
Planner ~15 min
Long-term project planning with the Gantt chart
Load a project, set dependencies and milestones, and assign resources - appointments flow to the planning board automatically.
Planner ~5 min
Plan a recurring appointment
Schedule a repeating job and manage exceptions without re-creating it every time.
Planner ~10 min
Optimize routes for a technician
Sequence a day of jobs by location and export the result for the field.

Business Central

The most common back-office connector - install it, sync it, fix it.

Admin ~30 min
Connect Business Central
Install the BC extension, point it at Dime.Scheduler, and verify the first sync.
Admin ~5 min
Diagnose a failed Business Central sync
Find the failing transaction, read the error, and apply the right fix.

Other integrations

Connect Dime.Scheduler to Exchange, Zapier, or any custom system over HTTP.

Admin ~45 min
Sync appointments bidirectionally with Exchange
Mirror appointments between Dime.Scheduler and resource Outlook calendars in both directions, with rules to control what flows where.
Developer ~20 min
Automate notifications with Zapier
Trigger a Zap on a Dime.Scheduler event and route it anywhere - Slack, email, your CRM.
Developer ~25 min
Set up a webhook connector
Push appointment events to any HTTP endpoint when the standard connectors don't cover your back-office.

Development

Feed data into Dime.Scheduler from your own code - pick an SDK or hit the API directly.

Developer ~30 min
Populate a fresh instance from code
End-to-end quickstart: insert resources, filter groups and values, indicators, jobs and tasks - and wire up the assignments between them.

Frequently asked questions

How do I find the right recipe?
Use the role filter at the top of the recipe list to narrow down to Admin, Planner, or Developer scenarios. Each card also shows an estimated time to complete.
What if my scenario isn't listed?
Browse the section that matches what you're trying to do - User docs for planning, Administration for setup, Integrations for connectors, Develop for SDK and API. If you still can't find it, contact support.
Are the steps in a recipe required to be done in order?
Yes. Recipes are sequenced so each step builds on the previous one - for example, you can't assign a filter value to a resource before the resource and the filter value both exist.
Can I follow a recipe in the sandbox first?
Yes, and we recommend it. The sandbox environment behaves the same as production but lets you experiment without affecting live data. Most recipes work identically in either environment.

Don't see your scenario?

These cover the most common tracks. Browse the section that matches what you're trying to do, or contact support and we'll help you find the right path.

Contact support