Data Structure for Recurrence Appointments

Here is how our current database is structured for events -

The recurrence Id refers back to itself. The Id of the topmost row. Here is sample data on what all I have in the recurrence data -

If I try to run the application the first record shows as recurrence. The future records show broken links as follows -

Is the above because it has filtered out the first record? Are we supposed to bring back the entire or the parent record?

Now if I double click on it I get error saying Id not found which does make sense since the original record was not brought in.
But if I click the original record which is 59 in this scenario and click on Edit Series the browser hangs. 

Can someone explain to me what data format is this expecting to be returned back from the database?

Thank You,

Regards,

Ameet 


1 Reply 1 reply marked as answer

RV Ravikumar Venkatesan Syncfusion Team April 5, 2021 12:38 PM UTC

Hi Ameet, 

Greetings from Syncfusion support. 

We have validated your reported problem “Data Structure for Recurrence Appointments” at our end. By default, the parent recurrence event alone stored in the DB as shown below. Individual occurrences of the Recurrence appointment are rendered based on the RecurrenceRule value. 

 

If we are editing an occurrence from the recurrence series the appointments are stored in the DB as shown below. The Id value of the parent event is added to the edited occurrence’s RecurrenceID field and the Date of the edited occurrence is added to the parent appointment’s RecurrenceException field. 

 

We have prepared a sample for your reference which can be downloaded from the below link. 

 
Note: Make sure the RecurrenceID field type is not a non-numeric value. 


Kindly try the above sample and UG links and get back to us if you need any further assistance. 

Regards, 
Ravikumar Venkatesan 


Marked as answer
Loader.
Up arrow icon