I have a WebDataGrid that that only has a couple of rows, but the database query to get the data is very slow. Currently there is no way to speed up the database query. The grid will populate without problems, but when you try to click on a header to sort the grid, it waits about 20 seconds and then displays an alert box with no text.
After using FireBug to step through the javascript I see were it sets a 20 sec timeout in Infragistics.Web.UI.IG.CallbackRequestHandler, and I see where there is a property to change this timeout in Infragistics.Web.UI.IG.ControlCallbackManager, but I do not know how to access this javascript object to change that timeout.
I saw another post to change the time for the WARP using ig_shared.getCBManager()._timeLimit = 60000; But that doesn't work with the WebDataGrid.
Any help would be greatly appreciated.
Thanks, Doug
Hello Doug,
The callback manager is referenced by each Aikido control through a protected js field: _callbackManager. So to increase the timeout you can do the following:
$find("WebDataGrid1")._callbackManager.setTimeout(60000);
I'm using Infragistics 11.2 and tried to set my WebDataGrid timeout using the following code:
$(document).ready(function() { $find("wdgMyWebDataGrid")._callbackManager.setTimeout(60000);});
However, on load, I receive the following Javascript error: '_callbackManager' is null or not an object. Any idea why?
Hi,
The reason you are getting this exception is be cause you are trying to do this in the document ready event. WDG has not finished initializing at this point yet. Please handle the WDG's Initialize client event and set the timeout there.
Thanks,
Olga
I am having the same issue. I have set the timeout to 60 seconds like this:
$find('WebDataGrid1')._callbackManager.setTimeout(60000);
I have this being set in both of these methods:
When I go to page two of my grid, when it has 40,000+ records, the AJAX spinner spins for 60 seconds then I get the error message "Server does not respond". Without the above changes I get the same error in 20 seconds. So it seems like it is helping, but I'm still missing something.
I am using the 13.1.20131.2107 version of the WebDataGrid.
Thank you,
Gregory