I noticed that under the known issues that there is an issue with virtual scrolling where AJAX responses that are too long cause a failure in the JSON deserializer.
Is there yet a fix for this? If not, is there a schedule for correcting it? This is really starting to cause some serious problems for me.
A follow up to this, I have fixed the problem I was having, and although it may not apply in the case of every instance of this problem, I thought I'd pass it along.
The issue seems to become pronounced if using the grid with EnableAjaxViewState set to true. In cases such as this, depending on the contents and structure of the grid, even setting the RowCacheFactor to its minimum value of "1" may cause the issue to appear.
For the issue I was having, I was using the grid to view data only, not for editing. After examination of the view state information, it became clear that view state on an AJAX retrieve could be in the multiple megabytes of data. Microsoft notes a hard limit on the amount of data that the JSON serialization is permitted to transmit on a response which this amount of data could easily exceed even for the simplest grids with minimal data.
If suitable to your application, setting EnableAjaxViewState to false seems to have no ill effects in this scenario. In fact, the amount data round-tripped was reduced such that I could increase the RowCacheFactor to a more reasonable value and still introduce no ill effect.
What was particularly puzzling was that problem may or may not exist depending on the machine to which machine the web site was deployed. Development machines, on the large and whole, did not have this issue, while web sites on machines without dev environments had this problem. I am wondering if some default gets set upon installation of the controls versus a simple deployment scenario, of course, this is a question for Infragistics, I'm just speculating there.
At this point, however, I'd like to note that, once again, the help materials available to diagnose this problem were grossly inadequate. It is particularly frustrating to have all of these options in the control without knowing which combinations are appropriate for various scenarios, or in the case of the EnableAjaxViewState property, not much indication at all of what it can affect. Previous issues have also centered around the appropriate settings of view states, AJAX, etc. for a given scenario.