- 2 minutes to read
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.
This document provides examples of the data sources, which should be used to store appointments and resources maintained by the DXScheduler Suite for WPF. This topic contains several sections, describing the data table structure for a particular data provider.
Note that not all data fields mentioned in this document are required for your application. For example, if only non-recurrent appointments are used, the "RecurrenceInfo" data field may be omitted. For the Appointments data source, the following fields are mandatory:
- the identity field, which is mapped using the AppointmentMapping.AppointmentId mapping
- the start of the appointment, which is mapped to the Appointment.Start appointment property using the AppointmentMapping.Start mapping
- the end of the appointment, which is mapped to the Appointment.End appointment property using the AppointmentMapping.End mapping
The field names you choose may differ from those listed below. You have to provide proper field mappings via the AppointmentStorage.Mappings and ResourceStorage.Mappings properties to ensure correct operation.
You can define any number of custom fields for your specific purpose, and map them to the appointment's custom properties via the AppointmentStorage.CustomFieldMappings and ResourceStorage.CustomFieldMappings. In the data table schemas shown below, the CustomField1 field is not mandatory, it is listed as a sample field to illustrate the concept.
It is not necessary to define a relation between Appointments and Resources tables, because the SchedulerControl simply stores the appropriate Resources.ResourceID field value in the Appointments.ResourceID field if all data fields are mapped correctly.
If resource sharing is enabled (the SchedulerStorage.AppointmentStorage.ResourceSharing property is set to true), the ResourceID field will hold xml string data, so its data type should be changed accordingly.