Date Dates tier

Create a dedicated child object to store selected dates. It only needs two custom fields — a Date field and a Lookup back to the parent record. Optionally add an End Date field for date range consolidation. For example, a Trip_Date__c object with these fields:

Drag the Date component onto your page in App Builder and configure these key properties:

• relatedObjectApiName — API name of your date object, e.g. Trip_Date__c
• dateFieldApiName — the Date field on that object, e.g. Date__c
• relationshipFieldApiName — the Lookup field back to the parent, e.g. Trip__c
• endDateField — optional End Date field for range consolidation, e.g. End_Date__c
• showInline — set to ON to show the calendar directly on the page (recommended)
• preloadExistingDates — set to ON to show previously saved dates when the page loads
• saveButtonLabel — customize the save button text, e.g. "Save Dates"

Or use the Setup Wizard and set just one property:

• configName — name of a saved configuration (e.g., PTO_Vacation_Requests). The component loads all settings from that Custom Metadata record.

By default the calendar stays expanded after Save, taking up the same space whether the user is actively picking or just reviewing. To collapse it into a small summary card after Save (and let users click the card to re-expand), set both:

Use this when the picker is one of several elements on a record page and you want it to step out of the way once the user has saved their picks.

If you want the component to auto-save records, set up the same child object as the Record Page section above (Date field + Lookup). Then create a Flow variable to capture the selected dates:

Add a Screen element in Flow Builder, drag the Date component onto it, and configure:

• label — button text that opens the picker, e.g. "Choose Travel Dates"
• modalTitle — title at the top of the calendar modal, e.g. "Pick Your Dates"
• showInline — set to ON to embed the calendar directly in the screen
• relatedObjectApiName — your date object, e.g. Trip_Date__c (for auto-save)
• dateFieldApiName — the Date field, e.g. Date__c
• endDateField — optional End Date field, e.g. End_Date__c
• relationshipFieldApiName — the Lookup field, e.g. Trip__c
• selectedDates (Output) — wire to your {!selectedDates} Text Collection variable
• outputAsJson — set to ON if you want grouped date ranges, then wire selectedDateRangesJson to {!dateRangesJson}