Hi Darren,Thanks for your update.We can parse the recurrence rule using explicitly created new generic utility class RecurrenceHelper in the project. To make use of this generic class in your sample, please refer this below KB link and refer it in your sample.https://www.syncfusion.com/kb/5390/how-to-parse-the-recurrencerule-in-server-side (The RecurrenceHelper Class is available in the sample link provided in this KB). Within this utility RecurrenceHelper class, GetRecurrenceDateTimeCollection method is defined which generates the date instances based on the RecurrenceRule and start date of the appointment. Using these auto-generated date collections from this method, we need to manually create the individual appointment instances as mentioned below in the code example,<Code>if (value.Recurrence!=0) // this code block will execute only for recurrence appointment{//Pass the recurrencerule string and the start date of the appointment to this method that will return the dates collection based on the recurrence ruledates = RecurrenceHelper.GetRecurrenceDateTimeCollection(value.RecurrenceRule, Convert.ToDateTime(value.StartTime)).ToList();// Now, the variable “dates” contains the date collection, with which the appointment instances are needed to be created manually.var diff = endTime - startTime1;for (var i = 0; i < dates.Count; i++) // this loop is used to create the appointment instances for the generated dates{startTime = Convert.ToDateTime(dates[i].AddHours(startTime1.Hour).AddMinutes(startTime1.Minute)); //start time for each occurrences will be calculatedendTime = Convert.ToDateTime(startTime.AddHours(diff.Hours).AddMinutes(diff.Minutes)); //end time for each occurrences will be calculatedMultipleResource appoint = new MultipleResource()// Appointment object creation{Id = value.Id + i,StartTime = startTime,EndTime = endTime,Subject = value.Subject,Recurrence = 0,AllDay = value.AllDay,RecurrenceRule = value.RecurrenceRule};db.MultipleResources.InsertOnSubmit(appoint);}}</Code>We have prepared the sample for your reference which can be download from the below location.In the above sample, we have stored the recurrence appointment (including its occurrences) as normal appointment (without repeat option) in the database. Initially, we used to store only the parent recurrence appointment (as single appointment) in the database and by using that parent appointment recurrence rule, we have internally processed to create the other occurrence of that recurrence appointment in the Schedule control. It is possible way to achieve your requirement and it is not recommended.Regards,Karthigeyan
Thank You for the insight....
Yes, understand it's not recommended... but for what I am utilizing it for... it's required... :)