[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)

Observable Collection


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.

When you consider the type of item in a collection, make sure that its properties can be mapped to the Scheduler Storage fields in a straightforward way, i.e. the property value type must correspond to the data type used in the mapping. This rule prohibits the use of the System.Collections.ObjectModel.ObservableCollection<T><Appointment,> collection as the data source because the mapping AppointmentMappingInfo.RecurrenceInfo requires mapped field of type string, not the RecurrenceInfo data type. Review the code snippet below for information of data types required for particular mappings.

Appointment and resource objects are represented by the ModelAppointment and ModelResource class instances as follows.

The SchedulerViewModel class exposes the generic collections of these objects (the ObservableCollection<ModelAppointment> and the ObservableCollection<ModelResource>) via its properties. The SchedulerViewModel class is specified as the window's data context. The DataSource properties of the AppointmentStorage and ResourceStorage instances are bound to the corresponding properties of the SchedulerViewModel in XAML.

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