I was going through ExceptionDate. So when I edit a recurring event and click on "only this event", I can see in the payload it adds exception dates. So for an event I should save this as a DateTime field in database or is it a list of exceptional dates?
And when we call load from crudManager, how should we send it in the Json. I was not able to see a json sample with exception dates.
I had created a string field exceptionDates in DB.
I am using the asp.net core demo as backend.
So first time when I try to update an occurance in the reccuring events, I see that it send the exception dates in the updated object and saves in the db.
Next time when I try to update another event in the same recurring events, I get error.
The json that is send is
backend expects a string and client passes array of strings.
Also why does when we edit second time, that event should have a exception date? It should be null right in the added object?
I cannot reproduce this issue on backend demo with recurrence enabled. Probably server doesn't tell client exception dates are updated.
e.g. Assuming you're using crud manager, response to this request:
Actually the array of strings I am converting to string before inserting to db. Hope that step is fine.
Model is used in deserializing JSON into class instances. If you want to change field type on the backend you'll have to use two fields: one to serialize/deserialize JSON and other to store data to DB. Please refer to the net core json library documentation. This question is really out of the scope of this forum as it is related to .NET Core.
Speaking of exceptionDates constantly appearing in sync request, we'd need a runnable test to inspect this behavior, because I cannot reproduce it on our end. Please provide one and we will take a look. Backend is not required, you can include 1-2 server responses instead.