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:
- the identity field, which is mapped using the AppointmentMappingInfo.AppointmentId mapping;
- the start of the appointment, which is mapped to the Appointment.Start appointment property using the AppointmentMappingInfo.Start mapping;
- the end of the appointment, which is mapped to the Appointment.End appointment property using the AppointmentMappingInfo.End mapping.
When working with recurring appointments, the mandatory fields in addition to the listed above are :
- the recurrence info field, which is mapped to the Appointment.RecurrenceInfo appointment property using the AppointmentMappingInfo.RecurrenceInfo mapping;
- the appointment type field, which is mapped to the Appointment.Type appointment property using the AppointmentMappingInfo.Type mapping.
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.