When a record is loaded with a recurrence starting outside the scope of my base view (current week), it'll duplicate with a new starting date corresponding to the first date of my base view and will be send through our sync API as a new record. Recurring event created in the current week will not be duplicated after load API.
We use a custom record model extending the EventModel just to add some new fields.
Thanks for reaching out and welcome to our forums.
Could you provide more context regarding how to reproduce the issue that you're mentioning? Are you able to reproduce that on one of our demos? If not, could you please provide a sample project for us to debug?
I've made some progress on my side and I've figured out why I had this duplicate. When creating my event bryntum adds this to my UNTIL recurrence rule.
You can see the screenshot. Unfortunately I'm not able to provide you with any code.
Hi, could you please send us request and response of these operations? Are you sure you saved all data that backend got?
PS: I can't reproduce your example because I don't have access to the data.
You have source code for all examples in /examples folder of our source code you downloaded in CustomerZone. Feel free to review, apply required changes and share here.