MultiDatePick User Guide

1. The three components: when to use each

MultiDatePick ships three Lightning Web Components on one shared base. Pick the one that matches your data.

Feature comparison

Features stack. Everything on Date is also on Date Time and Booking. Date Time adds times. Booking adds resources and capacity.

2. Record shapes: when to use each

A record shape is how a selection turns into records. It comes from three independent choices, and every combination works.

The Setup Wizard names six shapes: one record per date, one per date range, one per time block, parent plus sub-blocks, single resource and multiple resources.

Worked examples: answer the 3 questions

Answer three questions per scenario to land on a shape. The Setup Wizard asks the same three.

The grid: every combination

Pick the row for your time and resource needs. The column depends on whether End Date Field API Name is set. Every cell is a valid setup.

Bottom line: any combination of the three choices works. If your scenario is not a named pattern, set each choice on its own and the component does the rest.

3. Setup Wizard walkthrough

The Setup Wizard saves a configuration once. Type its name into Config Name on any page or Flow screen and that placement uses it. Change the config and every placement follows.

1. 1 Name & Type
2. 2 Object & Fields
3. 3 Time Fields
4. 4 Status & Display
5. 5 Review & Save

Choose a start

The Create New tab offers two paths. Walk me through it asks three questions and picks the component and shape. Configure all properties opens every setting. Two more tabs sit beside it: Existing Configurations to edit a saved config, and Import to paste one from the Config Library.

Step 1: Name & Type

Pick the component (Date, Date Time or Booking) and name the config. The name is what you type into Config Name later. This step also sets the views: the default view, which views the switcher offers, and the Timeline and Agenda options.

Step 2: Object & Fields

The big one. Pick the object that holds the records, its date field, and the relationship field back to the parent. Optional fields add ranges, resources, capacity, sub-blocks and blocked dates. Booking configs set the resource object, capacity field and business hours here too.

Step 3: Time Fields

Date Time and Booking only. Map the start and end time fields, then set the Time Interval (any interval works; 15, 30 or 60 minutes are typical), the earliest and latest time, the display mode, and what happens on a conflict.

Step 4: Status & Display

Status field and colors, statuses to hide, statuses users may pick, hover fields, Edit Mode, record naming, button labels, calendar size and limits such as Max Dates Allowed.

Step 5: Review & Save

Check the summary, try the live preview, then click Save Configuration. The wizard deploys the config for you in 30 to 60 seconds. Add an optional description when it finishes.

Existing Configurations and Import

Saved configs list on Existing Configurations: click one to edit or export it. The Import tab takes the JSON from any Config Library card, or an export from another org.

4. Permission sets & access

The package ships three permission sets. Assign them in Setup, Permission Sets.

The components run in each user's own permissions, so users also need access to your objects and fields:

• Objects: Read and Create on the object the records save to, plus Read on any resource, closure or child object the calendar reads.
• Fields, read: every field the calendar shows (date, status, hover fields).
• Fields, edit: every field it writes (date, times, status, second picklist, name field, the parent lookup). A field the user cannot edit fails the save, even when reads work.
• Referenced records: at least Read on the parent and resource the new record points to.

Each error message and its cause is on Troubleshooting: access errors. Guest sites need a few extra steps: see Public guest pages.

5. Click to Save vs Flow-Managed Save

There are two ways to save. Pick the one that fits the placement.

Click to Save: the four settings

The Setup Wizard fills these in. When all four have a value, the Save button appears.

Which parent record a page uses, and when to pick it in a Flow instead, is covered on App, Home & Experience Pages.

Flow-Managed Save: the outputs

Leave the four settings blank. The Save button hides and the selection comes out through these Flow outputs:

Pass the JSON to Parse Date Entries from JSON. It returns a list you can Loop over, with a from date, to date, start time, end time and resource Id on each item. Step by step: Flow recipes.

Saving only adds

Click to Save only creates new records. Deselecting a date never deletes a saved record, so a wrong click cannot lose data. To change or remove records, use Edit Mode or the related list.

6. Status colors & edit mode

Status colors and filtering

Color records by any picklist on your object, hide some values, and limit what end users can pick.

Edit mode

Turn on Enable Edit Mode and an Edit Dates button appears. In edit mode users can:

• See existing records as cards with their date and status
• Click dates to add their records to the edit set
• Change the date, times, resource or status, and the record updates
• Delete with a two-click confirm, so nothing goes by accident

7. Views: five layouts, one component

Every component draws five layouts. They read the same records through the same field mappings, follow the same conflict rules, blocked dates and business hours, and save the same way. Switching views changes how records look, never what they mean.

The five, and the question each answers

Settings

A different view per page

The view is a setting on each placement, so the same records can look different wherever they appear. One install, one set of field mappings.

Edit mode works in every view

With Enable Edit Mode on, the Edit button shows in every view. Click a record in Timeline, Week or Agenda to add it to the edit set, just like a date on the month calendar. A bulk status change from Timeline works exactly like one from the calendar.

Timeline: collapsed rows

When a resource has overlapping bookings, its row collapses to one strip with an N at once chip. A twisty opens one lane per booking. Collapsed rows still accept drag, hover and click.

Timeline: drag to reschedule

With Enable Edit Mode on, Timeline bars drag. Grab the middle to move a booking to other days. Grab an edge to change its start or end. The bar shows where it will land and saves when you let go. In Day zoom the same gestures change the times.

Schedule people, not just rooms

Resource Object API Name takes any object. Set it to User and Timeline becomes a roster, Week a shift grid and Utilization a team capacity dashboard.

• User has no standard capacity field. Add a custom one (for example Daily Capacity) to see Utilization in percentages.
• Map Business Hours Start Field and Business Hours End Field to User fields and the Week grid follows each person's own hours.

The Config Library has two ready-made examples: Team Capacity Planning and Staff Shift Roster.

8. Resource booking & capacity (Booking component)

Single resource

Users pick one resource from a dropdown. The time grid loads that resource's bookings and capacity.

Multiple resources

Turn on Allow Multiple Resources and the dropdown becomes checkboxes. The grid shows only slots open on every checked resource, and Save books them all at once.

Capacity

Let several bookings share a slot, with live 3/5 badges. A full slot stops taking bookings.

Conflicts

Conflict Behavior decides what happens when a picked slot is already taken. Conflict Look-Ahead Days sets how far ahead to check (default 360).

A closure always wins. Nothing saves onto a blocked slot, even with Allow.

9. Limiting what users select

Cap how much one person can pick, by dates or by time slots.

10. Blocking dates, times & resources (closures)

Any calendar can read closures from another object and grey out the dates, time slots or resources they cover, so users only book when you are open. Point a few settings at the closure object and the component does the rest. Whole-day blocks work on all three components. Time and resource blocks need the time grid of Date Time or Booking.

Blocking vs. hiding: what's the difference?

The two sound alike but do opposite things. Blocking takes availability away: the slot shows but cannot be booked. Hiding takes records out of view, which frees their slots.

The blocked-dates settings

Three levels of blocking

1. Whole day: a closure with no times greys out the whole date. All three components. A closed date stays closed even if it already has bookings.
2. Part of a day: a closure with a start and end time blocks just those slots. The rest of the day stays bookable. Blocked slots show once a date is selected.
3. One resource: a closure pointing at a resource closes only that resource. In a single-resource view the slot is struck through. In the combined view it gets a small corner flag and stays bookable on the open resources.

Using the time grid? You want part-of-day blocks. Whole-day blocks suit date-only pickers.

Two patterns for the closure object

• Same object, flagged by status: point Blocked Dates Object at your booking object and filter Status = Cancelled, so cancelled bookings double as closures. Simplest, but every calendar on that object shares them. See the Holiday Aware Appointment Booking config in the Config Library.
• A dedicated closure object: an Office Closure object with a date, optional start and end times, a Region field and an optional resource lookup. Each calendar filters by its region, and a closure can target one resource. See the Time-Aware Resource Closures config.

To let people block their own time (an owner blocking a morning, say), place a Date Time component that saves to the closure object on an internal page or site.

How blocked slots behave

• Look: a fully closed slot is struck through and greyed. A slot closed for only some of the picked resources gets a corner flag.
• Selection: a fully closed slot cannot be clicked or dragged over.
• Save: nothing saves onto a closed resource, date and time. With multiple resources, only the closed one is left out; the open ones still book.

One closure table, many calendars

Give the closure object a tag field (Region, Location, Building) and put the same field on your resources. Each calendar then uses Resource Filter Field / Value to show its own resources and Blocked Dates Filter Field / Value to read its own closures.

11. Public guest pages (Experience Cloud)

Put a component on an Experience Cloud site and anyone can book without logging in. Do all five steps before testing as a guest.

1. Object permissions. Give the site's guest user Read, plus Create if guests submit, on each object. Salesforce never lets guests edit or delete records, so keep edit, cancel and delete pages for logged-in users.
2. Field-level security on every field the component touches, including resource business-hours fields and closure time fields. One missing field stops the resource or closure query.
3. A guest sharing rule (Read) so the guest can see the records. The object's external org-wide default must be Private for the rule to apply. A rule deployed as metadata needs one click on Recalculate in Setup, Sharing Settings.
4. Apex class access to MultiDatePickController on the guest profile. The component loads its data through it.
5. Activate the site. Publishing and activating are separate steps.

• Which record guests see: a public page uses Static Parent Record Id, so every guest books against the same parent (one office, location or resource). For a record per visitor, drive it from a Flow with a URL parameter. True per-user calendars need logged-in users.
• Contacts and Accounts: Salesforce restricts guest access to them heavily. Book guests against a custom object, or use an authenticated site.
• Several components on one page: they do not live-sync. Add a refresh prompt between them so a block made in one shows in the next.

Placement steps are on App, Home & Experience Pages. A full worked site is on Experience Cloud Booking.

12. Common gotchas (FAQ)

Seeing a banner, a missing Save button or an empty calendar? Troubleshooting shows each message with a screenshot and the fix.

My status colors aren't applying

Check three things. (a) Is Status Field the exact picklist API name? It is case sensitive. (b) Does Status Colors use the format Value:#hex, Value:#hex with no quotes? 'Confirmed':'#22C55E' breaks it silently. (c) Do the records actually have a value in that picklist?

Records save with unexpected names

Check Record Name Field: if the field is short, long names get cut. Check Append Date to Record Name: when on, the selected date and time are added to every name.

How do I hide Cancelled records from the capacity grid?

Set Hide Records With Status to Cancelled, or a list such as Cancelled,Rejected. They drop out of the calendar and the capacity count.

What's the difference between blocking and hiding?

Blocking (closures) keeps a date, time or resource visible but unbookable: holidays, maintenance, a closed room. Hiding removes records such as Cancelled from the calendar and capacity, which frees the slot. See Blocking vs. hiding.

The Edit button isn't appearing

Turn on Enable Edit Mode. That is the only requirement, on all three components. A Status Field is optional; it only adds a status dropdown in the editor. If the button is still missing, the page or the config has Enable Edit Mode off.

I only want some resources (rooms, not equipment)

Use Resource Filter Field and Resource Filter Value. One value: field Active__c, value true. Several values (OR): North,South. Several fields (AND): field Type__c;Active__c, value Conference Room;true.

Date Time keeps showing one shared time picker

Time Display Mode is the setting to use: Grid or Dropdown. In Grid mode every date shares the grid. For a separate time per date, choose Dropdown and turn on Allow Different Times Per Date.

How do I move from Flow-Managed Save to Click to Save?

Fill in Parent Record Id, Child Object API Name, Date Field API Name and Relationship Field API Name. Remove the Parse Date Entries from JSON action and the loop that created records. The component's own Save button now writes them.

I get an error toast with no detail

Open the browser's developer console and look for lines starting [MDP:ERROR]. The full error is always logged there, even when the toast is short.

13. Flow recipes

Everything here is built in Flow Builder. No Apex.

Loop over the selected dates

1. Add a Screen with the Date Time component. Leave the Click to Save settings blank.
2. After the screen, add the Parse Date Entries from JSON action. Pass it Dates With Times JSON (Output).
3. Loop over the action's list. Each item has a from date, to date, start time and end time.
4. Inside the loop, assign the values to a record variable and add it to a collection. Create the records once, after the loop.

Roll the first and last date up to the parent

Want the parent to show the earliest and latest child date? Pick the no-code route that fits your data.

More Flow patterns: Screen Flow Guide.

14. Object & field mapping

Each component page has a full object and field mapping diagram:

• Date: object mapping
• Date Time: object mapping
• Booking: object mapping

The components work with any object. The sample objects in the package (Schedule, Event, Resource, Sub Block) are only defaults. Point the settings at your own custom or standard objects with the right fields.

15. All properties reference

Every setting on the three components, by the label you see in Lightning App Builder, Experience Builder and Flow Builder. The API name sits under each label.

16. Security & accessibility

• Passed the Salesforce AppExchange Security Review.
• 100% native. Your data stays in your Salesforce org. No external servers, no callouts. See Trust & Security.
• Your permissions, always. Every read and save runs in the user's own access, so object permissions, field-level security and sharing are enforced on each record.
• Accessible. WCAG 2.1 AA, tested with axe-core. Full VPAT 2.5.
• 9 languages: English, Spanish, French, German, Japanese, Hindi, Portuguese (Brazil), Italian, Chinese (Simplified).

17. Questions or bugs?

Found a gap in this guide, or something broken? Email support@multidatepick.com.