I am working with the Radscheduler and building a calendar that has dynamic data. Since I cannot control how much data comes back from the database, during testing I am trying to overload the scheduler and have succeeded in doing so. When I bind over 2,900 appointments in a month view (it should be noted that these appointments have several custom attributes) it is breaking with a message like this...
Error during serialization or deserialization using the JSON JavaScriptSerializer. The length of the string exceeds the value set on the maxJsonLength property.
I have already tried setting the maxJsonLength to it's maximum value in web.config, so I think I am maxing out this.
1) Is there any way other than what I have mentioned above to increase the amount the Radscheduler can handle?
2) Is there an official amount of data that is a recommended maximum to bind to the Radscheduler?
3) When it errors out saying maxJsonLength, why is that the error? Does this have something to do with the way data is retained within the control itself?
Error during serialization or deserialization using the JSON JavaScriptSerializer. The length of the string exceeds the value set on the maxJsonLength property.
I have already tried setting the maxJsonLength to it's maximum value in web.config, so I think I am maxing out this.
1) Is there any way other than what I have mentioned above to increase the amount the Radscheduler can handle?
2) Is there an official amount of data that is a recommended maximum to bind to the Radscheduler?
3) When it errors out saying maxJsonLength, why is that the error? Does this have something to do with the way data is retained within the control itself?
1 Answer, 1 is accepted
0
Hi Chris,
The issue observed is caused by the fact that some browsers have difficulties handling larger amounts of javascript and that is why this error is thrown. It is a browser limitation and unfortunately there is no other workaround for it. There is no official amount of data that is a recommended maximum to bind to the RadScheduler because there are so much different scenarios of different views and appointments settings which may give different results in older and newer browsers.
Hope this will explain the issue.
Regards,
Plamen
Telerik
The issue observed is caused by the fact that some browsers have difficulties handling larger amounts of javascript and that is why this error is thrown. It is a browser limitation and unfortunately there is no other workaround for it. There is no official amount of data that is a recommended maximum to bind to the RadScheduler because there are so much different scenarios of different views and appointments settings which may give different results in older and newer browsers.
Hope this will explain the issue.
Regards,
Plamen
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.