This is probably the same or similar issue to http://forums.infragistics.com/forums/t/69401.aspx
And is also somewhat related to an earlier post I made here http://forums.infragistics.com/forums/t/69426.aspx
So since the grid is taking 2-5 seconds to load the data and since I have a hidden column, the column header that is hidden is appear as undefined until the data is loaded.
Thank you.
Actually I have tried putting a empty string "" as the header text but then I get a nasty null showing up, I would have to put " " in order for it to show up as a blank.
Hello Exceed,
The existing development issue logged by Borislav has been linked to your case. You will be notified automatically with updates regarding this matter.
Hi,Sure thing - I've logged internal bug with ID 113972 about this to our RnD team.PS: Just a suggestion: you can place an empty string for the Header Text of such hidden columns - that way you won't get that nasty "undedfined"
The workaround indeed works and yes it does seem weird to have to apply it to all the grids.
If you can submit this issue as a bug that would be great.
Thanks.
Hi Exceed,Thanks for pointing out that I had set hidden to FALSE for that column. You are correct about the issue - the hidden column is indeed shown with the 'undefined' header text while the grid waits for the 1st 50 records to come.This seems like a development issue, but also one that's very tightly-packed with the way the grid renders column headers when at least one is hidden.I can submit the issue to the RnD team if you wish.However, I can offer you a workaround that should fit right into your scenario - set 0 pixels width to the CallID column and still set hidden to TRUE. It might seem a bit weird, but it gets the job done.Please give this suggestion a go an let me know what's the outcome.Cheers!BorislavPS: Initially I wasn't able to see the problem because my browsers had cached the page data and the server where I host the project had also cached some data so everything was going lightning-fast (even under IE). It was only after a restart of the server and a purge of the browser cache that I was able to see the issue - this is a more of a note to anyone who's looking at this forum thread and has trouble reproducing the scenario.