Appointment with exceptions still showing up

5 posts, 0 answers
  1. Richard
    Richard  avatar
    20 posts
    Member since:
    Jun 2013

    Posted 20 Dec 2017 Link to this post

    Hi.

    Following the Database example I have built my own version of exceptions.

    I have managed to actually create, save to a database and recover to show an exception for a certain appointment. Now my problem is that the original occurrence still shows up.

    (Attached is the image: on tuesday you can see the exception, but above it is the parent occurrence. (the appointment is one with a recurrence rule of every weekday).

     

    Obviously, I am missing something but I don't get what...

     

    Thanks in advance.

  2. Stefan
    Admin
    Stefan avatar
    824 posts

    Posted 25 Dec 2017 Link to this post

    Hi Richard,

    Though I am not completely aware of the approach you are using so that the reported behavior is reproduced, you can remove the needed occurrence by utilizing the Remove method of the control. The topic is discussed in greater detail in the Delete Appointment article. Can you please take a look at it?

    Another approach would be to use the DeleteAppointment command. The list of available commands of the control is available here:Commands.

    Would such an approach be working for you or I am missing something?

    Regards,
    Stefan
    Progress Telerik
    Want to extend the target reach of your WPF applications, leveraging iOS, Android, and UWP? Try UI for Xamarin, a suite of polished and feature-rich components for the Xamarin framework, which allow you to write beautiful native mobile apps using a single shared C# codebase.
  3. Richard
    Richard  avatar
    20 posts
    Member since:
    Jun 2013

    Posted 30 Dec 2017 in reply to Stefan Link to this post

    Hi Stefan.

    Thank you for you answer.

    I was in the belief that some automatic mechanism implemented in the control would take account of which appointments should be shown in the UI and which ones won't (i.e.: show exceptions if they exist, and remove the master appointment at the same time given the existence of those exceptions), but  once I realized I needed to implement the inclusion of the exceptions, that made me suspect I should also implement the removal of the originals.

    I guess you indirectly answered my question... :-)

    Have happy new year!

  4. Richard
    Richard  avatar
    20 posts
    Member since:
    Jun 2013

    Posted 30 Dec 2017 in reply to Richard Link to this post

    The implication is:  I can't just Delete the appointment: Is a recurrent appointment for Mon, Tue, Wed, Thu and Fri, with an exception on tuesday. 

    I only have to remove it from the current list, so it is not shown. That is the logic I thought might be part of the control's logic. But it makes sense it is not...?

  5. Stefan
    Admin
    Stefan avatar
    824 posts

    Posted 03 Jan Link to this post

    Hi Richard,

    Thanks for the update.

    The Remove method of RadScheduleView provides an overload for removing an Occurrence only. On the other hand, you can fetch a given Occurrence through the AppointmentExtensions.GetOccurence method, as demonstrated in this forum thread. Does this correspond to your requirements?
    Regards,
    Stefan
    Progress Telerik
    Want to extend the target reach of your WPF applications, leveraging iOS, Android, and UWP? Try UI for Xamarin, a suite of polished and feature-rich components for the Xamarin framework, which allow you to write beautiful native mobile apps using a single shared C# codebase.
Back to Top