Parent Recurrence Id bug

2 posts, 0 answers
  1. towpse
    towpse avatar
    224 posts
    Member since:
    Mar 2008

    Posted 05 Jan 2010 Link to this post

    Hey there

    There is a bug that seems to affect deleting appointments
    When I bind teletik appointment objects to the scheduler, I use Guids for both the ID and Parent Recurrence Id (when appropriate) Properties.

    In the delete appointment method when I am deleting an exception occurrence that has a parent recurrence Id, as it stands I need to do this in order for the web service appointment framework to successfully locate the parent appointment:

                if (appointmentData.RecurrenceParentID != null) 
                { 
                    appointmentData.RecurrenceParentID = new Guid?(new Guid(appointmentData.RecurrenceParentID.ToString())); 
                } 

    Otherwise the parent Id is a string and a match is not found and an error thrown.
    The ID property, which I bind as a Guid, comes back as a Guid as expected in the AppointmentData object.

    Also as a side note, when does the RemoveRecurrenceExceptions get called in my web service?
    What do I have to do to Remove a Recurrence Exception?
    I just made the code to create  recurrence exceptions but when I delete that appointment it just deletes it as a normal appointment which is fine. I just need to make sure I have the case when I remove recurrence exceptions handled as well.


    Regards.
  2. Dimitar Milushev
    Admin
    Dimitar Milushev avatar
    555 posts

    Posted 08 Jan 2010 Link to this post

    Hi,

    I've logged the problem into our system and we'll investigate it and hopefully fix it soon.

    RemoveRecurrenceExceptions should be called when you reset the exceptions of a given series. Please refer to the attached screenshot.

    All the best,
    Dimitar Milushev
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
  3. UI for ASP.NET Ajax is Ready for VS 2017
Back to Top