One Time Appears As Recurring

[Kerry]

I am currently using the RadScheduler control to manage my own custom Appointments. The DataSource is set to an enumerable collection of my TSAppointment class. All the DataSourceField properties are set to the correct object properties. When I look at the SQL record or object record that is supplying Appointments to the Scheduler, the RecurrenceRule is NULL and the RecurrenceParentID is NULL. However, the appointment rendered on the Scheduler appears as if it were an edited instance in a recurring series. Specifically, it has the icon that looks like the recurring 'arrow' with a slash through it. Subsequently, when I double click to edit, it shows the confirmation dialog asking if I want to edit this instance or the entire series. Am I missing something?

[Plamen]

Hello Kerry,

 
Thank you for contacting Telerik support.

Yes indeed the issue seems quite unusual indeed. Please refer to this on-line demo where is explained how we recommend similar scenario to be implemented and where the described issue is not observed. If you still can't figure out what is causing the issue please send us the code used so we could inspect the issue and be more helpful in solving it.

Regards,
Plamen
Telerik

[Kerry]

I have a very similar setup with some differences.

First, my object group class inherits ICollection(Of T) instead of a List(Of T).

Second, I cannot use session variables, as our end users, more often than not, will have several windows open.

Third, I took the database structure from http://www.telerik.com/help/aspnet-ajax/scheduler-database-structure.html. According to the example at the link you provided, it looks like several of the fields are of different types. Fundamentally, this would mean quite a massive restructure for me. Though, I should have noticed something was wrong when my insert statement failed because the RecurrenceParentID being passed was a string. Could these data types be causing this issue?

[Plamen]

Hello Kerry,

 
You can refer to this help topic where this scenario is explained deeper. If you can't use session  will recommend to refer to some of the other databinding scenarios with RadScheduler.

As for your other questions -yes the fields are very important and if some of them are not set properly the functionality may be broken.

Hope this information will be helpful.

Regards,
Plamen
Telerik