public AppointmentPropertyMappingsCollection AppointmentPropertyMappings {get; set;}
In cases where the names of the properties on the underlying data object are all the same as that of the schedule object properties to which they are bound, a mapping can be automatically assumed to exist. In this case, no explicit mappings are necessary.
In the case where a property of the underlying data object has the same name as a schedule object property, but the developer does not want a mapping to exist, add an AppointmentPropertyMapping with a null value for the SchedulePropertyMapping.DataObjectPropertyName property.
In cases where the data type of the bound property does not match that of the corresponding schedule object property, conversion is attempted, but is limited by the functionality provided by the Convert class. For example, an appointment's Start property can be mapped to a field of type string (assuming the data contained therein is a valid string representation of a date/time). Similarly, the Id property can be mapped to a field of type integer, since the numeric value can be converted to a string.
In cases where the value of the bound property is not convertible to that of the schedule object property, the SchedulePropertyMapping.ConvertCallback and SchedulePropertyMapping.ConvertBackCallback methods can be used to convert data bi-directionally.
The following Infragistics.Scheduler.Appointment properties require mappings:
Target Platforms: Android 4.4+, iOS 8+
Development Environments: Visual Studio 2015+, Visual Studio for Mac Preview, Xamarin for Visual Studio 4.2+