Reminder Issue

[Nick]

I'm currently using the Scheduler with a RadDock popup for the Appointments. I have small issue which I'm trying to solve for 2 days now and its driving me crazy :)

Whenever I set an appointment with a reminder, the reminder pops out correctly. When dismissing it I simply set the value of the Reminder to NULL in the DB. Now, everything works fine as long as I'm in the main Scheduler page.
At this point if I click any other appointment, even one that doesn't have a reminder, the previous reminder pops out a few seconds after the RadDock opens. I double checked the Database - the value of the reminder is set to NULL after dismissing it.    

The dismiss Event is shown below: 

Protected Sub scheduler_ReminderDismiss(sender As Object, e As Telerik.Web.UI.ReminderDismissEventArgs) Handles scheduler.ReminderDismiss
    Dim followup As New FollowUp(e.Appointment.ID)
    followup.Notification = DbNull.Value.ToString()
    DBTool.UpdateFollowUp(followup)
    scheduler.DataSource = DBTool.PopulateFollowUpAtMainPage()
    scheduler.Rebind()
End Sub

Another problem that I have is that the ReminderDismiss event doesn't refresh the scheduler. The scheduler is included in the AjaxManager. When debugging I do see the ReminderDismiss Event but it looks like the "Rebind" event of the scheduler is not refreshing the control. Maybe this is causing the issue?




 

[Nick]

Ok - I was able to solve the popup problem. I didn't realize you have to bind the scheduler on every postback.

With that being said, why does the Dismiss Event doesn't refresh the Scheduler? 

Nick

[Peter]

Hi Nick,

When setting the DataSource property, you should use Databind() after this, instead of Rebind(). Can you try this way and let me know if this solves the problem?

All the best,
Peter
the Telerik team

[Nick]

This doesn't solve the problem. The Scheduler doesn't update.

[Peter]

Hi Nick,

I wasn't able to replicate this problem locally. If you can send us a sample via a support ticket, I will look into it and try to find the cause of the issue.

Kind regards,
Peter
the Telerik team