The getter returns a defensive copy so changes take effect only after assigning a definition back to this property. Assigning an unsupported definition throws an error without changing the active definition or rendered view.

Changing this property updates the visible date range and raises displayDateChanged.

Fields that are not supplied use the Scheduler defaults.

By default, the fields in the event data need to include the required start and end, and possibly subject and description as well. If the fields in the original data don’t meet the requirements or can’t be changed, you can use eventFields to map them.

For example, if the event data has startDate, endDate and title fields instead of start, end and subject, you can use:

const data = [
    {
        title: 'Event 1',
        startDate: new Date(2023, 0, 1),
        endDate: new Date(2023, 0, 1, 1),
        information: 'a sample event.'
    }
];

scheduler.eventFields = {
    subject: 'title',
    start: 'startDate',
    end: 'endDate',
    description: 'information'
};

The getter returns a defensive copy so changes take effect only after assigning a definition back to this property.

Assign an array or ICollectionView. When a collection view is supplied, filtering, sorting, paging, and collection change notifications are preserved.

These exceptions take precedence over workDays and {@link workHours}. The getter returns a deep copy.

For example, nonworkingTime = [{ start: new Date(2026, 6, 23, 12), end: new Date(2026, 6, 23, 13) }] marks the noon hour of July 23, 2026 as non-working.

Each descriptor maps an event field to an array or collection view of resource items. The getter returns a copy of the descriptor array.

Set scrollingSyncDirection to choose which axes are synchronized.

For predictable results, use the same definition on synchronized Schedulers. When synchronized Schedulers use different definitions, their scrollable ranges may be different. In that case, synchronization copies the current scroll offsets from the Scheduler that scrolled most recently. A Scheduler with a longer scroll range may therefore be clamped or moved backward when it receives a scroll offset from a Scheduler with a shorter scroll range.

When a synchronized Scheduler changes to a different definition, the new scroll element starts from the previous scroll distance restored by the browser/control refresh cycle before subsequent scroll synchronization is applied.

The default value for this property is true.

Set this property to null to use the browser's local time zone.

Each SchedulerViewItem supplies the button text and key. A built-in enum key uses its preset definition when definition is omitted. Custom string keys require a matching definition. Invalid items and duplicate resolved keys are ignored, preserving the order of the first valid occurrence. The getter returns a deep copy of each item with its resolved definition, so update the property by assigning a new array.

The default value contains Day, Week, Work Week, Month, Timeline Day, Timeline Week, and Timeline Month buttons using the current culture.

The value must contain exactly seven SchedulerWorkHours entries in Sunday-to-Saturday order. Each entry contains SchedulerWorkHourRange values for that weekday. An empty entry means that weekday is non-working.

The default value is null, which disables the weekly rule. Assigning null to the entire property leaves working time unrestricted by this source. Timed views use the selected entry to style each time slot, and summary views use it to style the corresponding day. When workDays is configured, workHours is ignored. The getter returns a deep copy, so mutating a returned range does not change the scheduler state.

scheduler.workDays = [
    [],
    [{ start: '09:00', end: '18:00' }],
    [{ start: '09:00', end: '18:00' }],
    [{ start: '09:00', end: '18:00' }],
    [{ start: '09:00', end: '18:00' }],
    [{ start: '09:00', end: '12:00' }],
    [],
];