Hello,
I wonder if anyone has found this. I had implemented a control with the RadScheduler, and a dynamic datasource. We used the trial version (2008.1.515.20). Everything was working OK, so we decided to purchase a few licenses; so when I upgraded to version 2008.1.619.20 the option 'Edit Series' throws an exception error "Object reference not set to an instance of an object". The method where this happens apparently is AdvancedTemplate.CreateAppointmentBasicControls(). I have implemented the server-side event "RadScheduler1_FormCreated" but it never reaches it. Editing an occurrence works fine, and also editing a simple appointment also works fine.
Any help would be appreciated.
Thanks,
Antonio.
I wonder if anyone has found this. I had implemented a control with the RadScheduler, and a dynamic datasource. We used the trial version (2008.1.515.20). Everything was working OK, so we decided to purchase a few licenses; so when I upgraded to version 2008.1.619.20 the option 'Edit Series' throws an exception error "Object reference not set to an instance of an object". The method where this happens apparently is AdvancedTemplate.CreateAppointmentBasicControls(). I have implemented the server-side event "RadScheduler1_FormCreated" but it never reaches it. Editing an occurrence works fine, and also editing a simple appointment also works fine.
Any help would be appreciated.
Thanks,
Antonio.
2 Answers, 1 is accepted
0
Hello Antonio,
I have tested the scenario locally, but I could not reproduce the problem.
The most likely reason is that RadScheduler cannot locate the "master" appointment of the recurrence series. This might be cause by a data-binding issue, but this is only a guess at this point.
We have not introduced any major changes in the data-binding code for the SP2 release. But it is possible that we have changed something that affect your case, as part of a bug fix.
It would be best if you can prepare and send us a minimal page that demonstrates the issue, so we can debug it.
Regards,
Tsvetomir Tsonev
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
I have tested the scenario locally, but I could not reproduce the problem.
The most likely reason is that RadScheduler cannot locate the "master" appointment of the recurrence series. This might be cause by a data-binding issue, but this is only a guess at this point.
We have not introduced any major changes in the data-binding code for the SP2 release. But it is possible that we have changed something that affect your case, as part of a bug fix.
It would be best if you can prepare and send us a minimal page that demonstrates the issue, so we can debug it.
Regards,
Tsvetomir Tsonev
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
antonio
Top achievements
Rank 1
Rank 1
answered on 25 Jun 2008, 04:37 PM
Hello Tsvetomir,
The latest release was not the culprit for this problem. Like you said, I had changed the routine that fetches appointments lately and the series record was not available to the program. I have corrected it and now it works OK.
Thanks,
Antonio.
The latest release was not the culprit for this problem. Like you said, I had changed the routine that fetches appointments lately and the series record was not available to the program. I have corrected it and now it works OK.
Thanks,
Antonio.