Hi Tony, sorry for the late reply. I've investigated this issue a bit more and found out that the problem is caused by the call to populate() in the handler to the event attached to the button to expand and collapse the grid in the header.

That looks like the reason why the rows are ordered correctly when the grid is loaded for the first time and it is hidden, while expanding it results in a wrong ordering. Removing the call to populate() in the handler to the click of the expand/collapse button seems to fix it, but it's not a clean solution.

I tried upgrading to 3.6 and the behavior is the same.

tony said:

Hello,

Which search module (method) do you use?

Please refer to docs and the important notes here:

http://www.trirand.com/jqgridw…..rch_config

I read the docs

Sorry?

Looking at the documentation here I see dataUrl mentioned:

This option is valid only for the elements of type select – i.e stype:'select'. The option represent the url from where we load the select element. When this option is set the element will be filled with values from the ajax request. The data should be a valid html select element with the desired options. By example the request should contain One Two. This is called only once.

But dataUrl, as reported by others, isn't working, while surl is. So I was just asking if the docs are out of date, or where I should look to see it documented.

Anyone?