SchedulerStorage.RefreshData() Method
Updates scheduler control to reflect any changes made in the data sources which store the appointments and appointment resources.
Namespace: DevExpress.Xpf.Scheduler
Assembly: DevExpress.Xpf.Scheduler.v24.1.dll
NuGet Package: DevExpress.Wpf.Scheduler
Declaration
Remarks
Important
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.
Appointments and appointment resources for the scheduler control can be stored in external data sources. To connect the scheduler control to these data sources, use the DataSource and DataMember properties of the AppointmentStorage and ResourceStorage objects.
By default, data from the data sources is automatically reloaded after each change is made to the data sources (for instance, when records are added, deleted or modified). Automatic data reloading can be disabled via the AutoReload properties of the AppointmentStorage and ResourceStorage objects. If this property is set to false, the scheduler control ignores any change notifications sent by the data source, and doesn’t automatically reload data. You need to manually call the RefreshData method to reload the data in the data source for the changes to appear in the scheduler control.
Note
When you call the RefreshData method, all appointments in the scheduler control are recreated. So, all appointments referenced in your code previously are disposed, and you should not use them.
Note for VB.NET users: an appointment, newly created via the SchedulerStorage.CreateAppointment method has its PersistentObject.CustomFields values set to Nothing. However after calling the RefreshData method, which loads data from the data source, the appointment custom field values are set to the values of the mapped data fields. If the data field does not contain any value, then the corresponding custom field value becomes DBNull instead of Nothing.