Frequently Asked Questions

MultiDatePick is a suite of three native Salesforce Lightning Web Components for multi-date selection, date & time scheduling, and resource booking. It installs as a managed package from the AppExchange - no custom code required.

Screen Flows, Lightning Record Pages, App Pages, Home Pages, and Experience Cloud (community) sites. The same component works across every surface - configure it once and place it where you need it.

No. The month grid is the default, but the same component renders five layouts: calendar (month grid), timeline (resources down, dates across), week (day by hour), utilization (capacity heatmap) and agenda (chronological list). All five read the same records through the same field mappings and save through the same path, so switching layout never changes what a booking means. Set the default with the view property and control which ones users can switch to with availableViews. More on the views.

Yes, and that is the point of it being a property rather than an org-wide setting. A recruiter's page can open on the week grid, a facilities page on the month grid with timeline and utilization available, and an operations wall display on the read-only agenda. One install, one set of field mappings, and no chance of two components drifting apart.

Yes. The resource lookup accepts any object, so pointing it at User turns the component into a staffing tool with no code change: Timeline becomes a roster, Week a shift grid, and Utilization a team capacity dashboard. Two notes: User has no standard capacity field, so add a custom one if you want the heatmap in percentages rather than counts, and mapping businessHoursStartField to a field on User gives each person their own working hours. The config library ships Team Capacity Planning and Staff Shift Roster as ready-made examples.

Yes. MultiDatePick installs as a namespaced managed package from the Salesforce AppExchange, so it upgrades cleanly and never conflicts with your existing components.

Date is simple multi-date selection (with range support). Date Time adds per-date time slots. Booking adds resources, availability checking, capacity, and conflict handling. See the component picker to choose.

Yes. The Booking component handles multiple resources, per-slot capacity ("3 of 5 left"), conflict detection, and multi-resource grids. See capacity tips.

Yes - point the component at any "closure" object. Whole-day closures grey out the calendar date; partial-day closures grey out specific time slots, optionally per-resource. See blocking tips.

Yes. All three components are Flow screen components, and a bundled Apex parser turns the selected dates into a Flow-loopable collection. See the Flow Cheat Sheet.

No. A built-in Setup Wizard walks you through configuration with a live preview, then deploys the config for you. You can also import ready-made configurations from the Config Library.

Minutes for a standard use case. Pick the component, run the Setup Wizard (or import a config), and place it on your Flow or page. The Getting Started guide walks through it.

On Lightning Record Pages it can auto-save selected dates to related records (additive-only, so nothing is ever deleted unexpectedly). In Flows, it outputs the selection for you to use however you like.

$20 per user/month, with a 30-day free trial.

Included. There's a single plan with every feature - Date, Date & Time, and Resource Booking all come standard. No upgrades, no feature gates.

Yes - a 30-day free trial through AppExchange Checkout. Get notified at launch to be first in line.

Yes. All three components are available in Experience Builder. See App / Home / Experience Pages and the public guest-site setup tips.

Nine: English, Spanish, French, German, Italian, Portuguese (Brazil), Japanese, Chinese (Simplified), and Hindi. The UI follows each user's Salesforce language.

Yes - built to WCAG 2.1 AA with keyboard navigation, ARIA labels, visible focus, and screen-reader support. See the accessibility page.

Enterprise edition and above (for Flows and Lightning Record Pages). It runs on Lightning Experience; the components are Lightning Web Components.