RadScheduler supports seamless integration with the RadODataDataSource controls which makes binding to OData feed an easy task.
In contrast to the standard WebService binding, the OData binding does not require serialized
AppointmentData objects. Instead, the developer is free to expose whatever objects they want as a JSON feed,
as long as the data is meaningful to the Scheduler.
Binding using the RadODataDataSource control is very similar the standard binding mechanism except for the fact that the RadScheduler is in Read-Only mode. The following properties could be set in order to map the exposed feed to the
DataModelID should resemble a model defined in the RadODataDataSource control.
The InitialContainerName property is now depricated and DataModelID should be used instead.