Booking

The Booking component requires two objects: a Resource object (what gets booked) and a Booking object (where reservations are stored).

Resource Object (e.g. Meeting_Room__c):

Booking Object (e.g. Room_Booking__c):

Drag the Booking component onto your page in App Builder and configure:

Resource Object Settings

• resourceObjectApiName — the resource object, e.g. Meeting_Room__c
• resourceNameField — display name field, usually Name
• businessHoursStartField — e.g. Business_Hours_Start__c
• businessHoursEndField — e.g. Business_Hours_End__c
• capacityField — optional capacity field, e.g. Capacity__c
• capacityAggregation — picklist: Combined (default) or Distinct. Controls how X/Y occupancy is computed when multiple resources are selected. Combined sums bookings AND capacities across resources — best when each resource is independent inventory (4 records across 4 rooms with capacity 5 each = 4/20). Distinct counts the MAX bookings on any single resource and uses the MAX single-resource capacity — so the same event booked across multiple resources counts as ONE (4 records across 4 rooms = 1/5), while multiple bookings on one resource still count separately (3 bookings on one room = 3). Best when one logical event spans multiple resources simultaneously. Recommended pairing: use conflictBehavior = 'block' with Distinct so the event only commits when all of its resources are free — skip would partially book it (run the event in only the open resources).
• allowMultipleResources — ON to let users book multiple resources at once
• resourceFilterField — optional. API name of a field on the resource object used to limit which resources appear in the picker. Pair with resourceFilterValue. Supported field types: Checkbox (Boolean), Picklist, Text, Long Text, Number, and Lookup. Use ; to combine multiple fields (AND). Examples: Active__c, Type__c;Building__c
• resourceFilterValue — optional. Value(s) the filter field must equal. , between values within ONE field = OR (IN clause); ; between values = AND across multiple fields. Booleans use true/false. Examples: true, Conference Room, North,South, Conference Room;North,South (Type = Conference Room AND Building IN North or South). The Setup Wizard auto-renders the matching control for the picked field — True/False dropdown for Booleans, dual-listbox for Picklists, free text for the rest.

Booking Object Settings

• resourceBookingObject — the booking object, e.g. Room_Booking__c
• bookingDateField — the Date field, e.g. Booking_Date__c
• bookingStartTimeField — e.g. Start_Time__c
• bookingEndTimeField — e.g. End_Time__c
• bookingResourceField — lookup to the resource, e.g. Meeting_Room__c
• relationshipFieldApiName — lookup to the parent, e.g. Contact__c

Or use the Setup Wizard:

• configName — e.g. Training_Enrollment or Desk_Hoteling

By default the booking UI stays expanded after Book. To collapse it into a small summary card after the user books (and let them click to re-expand), set both:

Useful on record pages where the booking widget should step out of the way once a reservation has been made.

Same two objects as the Record Page section above (Resource + Booking). Create these Flow variables:

Add a Screen element in Flow Builder, drag the Booking component onto it, and configure the same Resource and Booking Object settings as above, plus:

• bookingSuccessCount (Output) — wire to {!bookingSuccessCount}
• bookingConflictDates (Output) — wire to {!bookingConflictDates}