Hi all,
This one is driving me a bit batty and I cannot figure it out. Scenario is that we have one UltraWebGrid being displayed in an UpdatePanel. The grid will sucessfully retrieve and display data on first partial postback but any subsequent partial postback results in the data being lost and a Javascript error saying "igtbl_Grid.base.init is null or not an object"
Any thoughts or suggestions on this would be GREATLY appreciated.
Ooops I forgot some stuff.
The grid we have is placed inside a user control. And the UpdatePanel is placed outside of the user control.
Also I attempted the same thing with a WARP and I'm still having the same effect.
I am having a similar problem with a grid - when it is inside of a warp panel, on the first postback it comes up with no rows. The server side has row data, as demonstrated using an Excel Export after the grid posted back - the resulting xls file had the data I expected. No idea what is causing this right now - this was working in IF v6.3.1059 (the last version we used before upgrading.)
I have the feeling it might be a cause like that. We do have other 3rd Party JS. I'll have to dig around. I also know we do have another WARP in our Master Page. Could that affect other WARPs/UpdatePanels?
Really late Edit: Wow. I can't believe it was this. It was IE 8. I should have mentioned this in the beginning. I was using it in IE 7 mode but apparently that isn't exactly working exactly like IE 7 like I thought it was. I had another person try my code on their machine and it worked just fine. Well, if anything I might have pointed out a potential problem with upcoming IE 8. It still could be a problem with some other JS we're using/3rd party. Sorry about that. Thank you all for your assistance!
I was able to trace my problem down to a thrid party javascript called Prototype. I don't have the time on this project to look into what is causing the issue in the script, but removing the script reference from the page was sufficient to fix the issue I had.
It is really tough to tell without seeing a repro first... this could really be for a number of reasons. You may need to contact Developer Support with a small subset of your project reproducing the problem for additional comments/suggestions/fixed.