I am not quite sure what do you mean by "view model". There are several demos that could help you understand better the different sources of data for RadScheduler.
Generally, the main source of data for a RadScheduler is the Appointments information. It could be passed to the RadScheduler by using Generic list
, XML file and XML provider
, Database provider
, Entity data source
, Web service
, SQL data source
, on the other hand, provide additional information about appointments. For example, in a RadScheduler there could be several users that have appointments, or several rooms, where appointments are held. User is one resource type, while Room is another one. In the Appointments data, there is information about which are the user and the room for each appointment. At the same time, you could retrieve additional information for each user / room from a separate data source. When SQL data source is being used, in most cases these are three separate tables - an Appointments table, a Users table and a Rooms table which are related to each other.
I hope that the above helps you. If you have any further questions, please do not hesitate to contact us.
Do you need help with upgrading your ASP.NET AJAX, WPF or WinForms projects? Check the Telerik API Analyzer
and share your thoughts.