Hello!
I'm using advanced templates and own MSSQL DB for storing events. When I change date of one of recurring events, then double click on it to edit series and I click "Reset exceptions" exceptions are being deleted but in original Event in RecurrenceRule I'm still having "EXDATE:20080422T000000Z,20090422T000000Z".
How can I catch resetting exceptions event in AppointmentCommand command event?
Thanks
EDIT:
When I'm updating event I have "Update" in e.CommandName in AppointmentCommand event but when I'm resetting exceptions e.CommandName is empty.
I'm using advanced templates and own MSSQL DB for storing events. When I change date of one of recurring events, then double click on it to edit series and I click "Reset exceptions" exceptions are being deleted but in original Event in RecurrenceRule I'm still having "EXDATE:20080422T000000Z,20090422T000000Z".
How can I catch resetting exceptions event in AppointmentCommand command event?
Thanks
EDIT:
When I'm updating event I have "Update" in e.CommandName in AppointmentCommand event but when I'm resetting exceptions e.CommandName is empty.
1 Answer, 1 is accepted
0
Accepted
Hello GrZeCh,
Thank you for reporting this issue. Resetting the recurrence exceptions will not fire an AppointmentCommand event. Instead it will fire an AppointmentUpdate for the master appointment (to update the recurrence rule) and a number of AppointmentDelete events for the deleted exceptions. Or so it should. It turns out that there is a bug and the AppointmentUpdate event is not fired. Hence you do not get a chance to update the recurrence rule.
We have fixed this issue. Please, open a formal support ticket so we can send you a hotfix. Your Telerik points have been updated for your involvement.
Kind regards,
Tsvetomir Tsonev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Thank you for reporting this issue. Resetting the recurrence exceptions will not fire an AppointmentCommand event. Instead it will fire an AppointmentUpdate for the master appointment (to update the recurrence rule) and a number of AppointmentDelete events for the deleted exceptions. Or so it should. It turns out that there is a bug and the AppointmentUpdate event is not fired. Hence you do not get a chance to update the recurrence rule.
We have fixed this issue. Please, open a formal support ticket so we can send you a hotfix. Your Telerik points have been updated for your involvement.
Kind regards,
Tsvetomir Tsonev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.