Skip to main content

DevExpress v24.2 Update — Your Feedback Matters

Our What's New in v24.2 webpage includes product-specific surveys. Your response to our survey questions will help us measure product satisfaction for features released in this major update and help us refine our plans for our next major release.

Take the survey Not interested

Required Fields

  • 2 minutes to read

Note

You are viewing documentation for the legacy WPF Scheduler control. If you’re starting a new project, we strongly recommend that you use a new control declared in the DevExpress.Xpf.Scheduling namespace. If you decide to upgrade an existing project in order to switch to the updated scheduler control, see the Migration Guidelines document.

For the Appointments data source, the following fields are mandatory:

When working with recurring appointments, the mandatory fields in addition to the listed above are :

The required column in the Resources data table is the resource identifier, which is mapped to the IPersistentObject.Id property using the AppointmentMappingInfo.ResourceId mapping.

If you omit recurrence information data mapping (the AppointmentMappingInfo.RecurrenceInfo is not specified), the AppointmentStorageBase.SupportsRecurrence property is false, no recurring appointments will be displayed, and the commands and dialogs for creating and editing recurring appointments will not be available.

If you omit the data mapping of reminder information (the AppointmentMappingInfo.ReminderInfo is not specified), the AppointmentStorageBase.SupportsReminders property is false, no reminders will be displayed, and the appointment editing dialog will not contain the Reminder editor.

If you plan to implement import/export operations with MS Outlook or MS Exchange calendars, provide a special field in your data table. This field will store the EntryID for Outlook or Exchange messages. You are advised to set its type as a string with a length of at least 50 for MS Outlook or 130 for MS Exchange. The next generation of MS products may require longer identifiers, so use variable length fields to be on the safe side. For more information, refer to the Synchronization with Microsoft Outlook topic.