We have an ASP.Net RadFileExplorer integrated into our system and have noticed that once the number of files increases to 150 or more - suddenly we start getting "callback failed" when the user enters info in the "Filter By" (build-in control shown above the file list view in explorer) . Initially thought this was data related, but after experimentation appears to be a length limit of some type in the transfer, thus once the return size is larger than that limit - we get the error independent of the data - otherwise all works as expected. Strangely when I set a break on the error callback, I do see all the data has been transferred from the server as expected.
Is there a size limit on the return of the webresource call, or other limit ??? any tips on debugging this issue is appreciated.
1 Answer, 1 is accepted
Rank 1
Iron
Iron
I was able to figure out the issue. We do NOT use paging, thus is turned off. But the PageSize attribute is apparently still honored by the "Filter by" box. This is why we encountered the length limit, when we change the value from 120 to 9999, the problem went away, and then resurfaced when set back to 120.
Just an FYI to anyone else that might encounter this.
AllowPaging="False" PageSize="120"
