An object calendar surfaces records from any standard or custom object as calendar entries, using a date field to place them. Here is how a user creates one in Lightning Experience. Each user can create up to 10 of their own.
- Open the Calendar tab
Click the Calendar tab in the app navigation. If it is not visible, an admin may need to add it to the app or enable it for the profile.
- Start a new calendar
Click the gear or settings icon next to My Calendars in the left side panel and choose New Calendar.
- Pick the object
Select the standard or custom object whose records you want to show, for example Opportunity, Service Appointment, or a custom object. External objects are not supported.
- Map the fields
Choose the field that names each entry, the start date or date/time field, and an end date field if the object has one. Optionally apply an existing list view to filter the records.
- Save and toggle it on
Save the calendar. It appears under Other Calendars where you can show or hide it and change its color so its entries are easy to tell apart from your events.
The standard or custom object the calendar draws records from. External objects and some special objects are not eligible.
The record field whose value labels each entry on the calendar, such as Subject or Name.
The date or date/time field that decides where each record lands on the timeline.
A second date field that gives each entry a duration. It must fall after the start, or the record will not display.
An existing list view that filters which records appear, useful for keeping a busy object under the display cap.
- An object calendar shows a capped number of items per view (Salesforce documents 150). Use a narrow list view so important records do not fall past the cap.
- If the end date field is earlier than the start date field, the record silently does not appear on the calendar.
- Object calendars respect record sharing and field-level security, so a user only sees records they could already open. They never widen access.
- Each user creates and owns their own object calendars, up to 10, so there is no single org-wide object calendar to manage centrally.