[Expand]General Information
[Expand]WinForms Controls
[Expand]ASP.NET Controls and MVC Extensions
[Expand]ASP.NET Bootstrap Controls
[Expand]ASP.NET Core Bootstrap Controls
[Collapse]WPF Controls
 [Expand]What's Installed
 [Expand].NET Core 3 Support
 [Expand]Common Concepts
 [Expand]MVVM Framework
 [Collapse]Controls and Libraries
  [Expand]Data Grid
  [Expand]Ribbon, Bars and Menu
  [Expand]Charts Suite
  [Expand]Pivot Grid
  [Expand]Rich Text Editor
  [Expand]Tree List
  [Expand]Gauge Controls
  [Expand]Map Control
  [Expand]Layout Management
  [Expand]Windows Modern UI
  [Expand]Data Editors
  [Expand]Navigation Controls
  [Expand]Spell Checker
  [Expand]Property Grid
  [Expand]PDF Viewer
  [Expand]TreeMap Control
  [Expand]Gantt Control
  [Expand]Diagram Control
  [Expand]Windows and Utility Controls
   Dialogs, Notifications and Panels
  [Collapse]Scheduler (legacy)
   [Expand]Getting Started
    [Expand]Scheduler Elements
     Pop-up Menus
    [Collapse]Data Binding
      Microsoft Access Database
      Microsoft SQL Server
      Collection of Custom Objects
      XPO (eXpress Persistent Objects)
      Entity Framework Code First
      Observable Collection
    [Expand]Supported Formats
    [Expand]Styles and Templates
     Time Zones
     Product Class Structure
     Scheduling Basics
   [Expand]Visual Elements
 [Expand]Scaffolding Wizard
  Redistribution and Deployment
  Get More Help
 [Expand]API Reference
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Office File API
[Expand]Report and Dashboard Server
[Expand]eXpressApp Framework
[Expand]eXpress Persistent Objects
[Expand]CodeRush Classic
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation
View this topic on docs.devexpress.com (Learn more)

Data Binding


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 required column in the Resourcesdata table is the resource identifier, which is mapped to the IPersistentObject.Id property using the AppointmentMapping.ResourceId 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 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.

Is this topic helpful?​​​​​​​