The reload parameter if set to false does not reload the grid only if you are in the same sortname and same sortorder - this mean is your current grid setting is : column1 and the sortorder is asc, the grid will not be reloaded only if you

In all other cases you will got with reloading.
Please look here

Regards

http://jsfiddle.net/Jq2HR/

In making that I learned that the issue only exists when sortGrid is executed within the loadComplete event handler. If it's executed separately then subequent navigation works fine. So whatever is happening that's messing up the behavior must be running internally after the loadComplete event fires, but since that's the last event in the data loading process, there's no option for me to execute sortGrid any later.

The only remaining option I can think of would be to set a timeout in loadComplete to execute sortGrid after jqGrid is finished doing whatever it does after that event. Seeing as though I'm just trying to fix a subtle visual this is a possibility, but might fall out of sync if a user paginates quickly, so clearly not ideal.

IMO the best solution would be for jqGrid to support server-side sorting defining. So if the server provides sort/order variables (or whatever is defined in prmNames) in the response, those will automatically overwrite whatever jqGrid already thinks sorting is. The server being the authorative source over how the data is actually sorted, it makes sense that it could tell jqGrid that for proper presenation. I actually expected this behavior to exist already and have returned sorting information this whole time...

Can you please post a simple demostration?

Thank you

Kind Regards

The idea to call sortGrid in loadComplete event is very dangerous. You will go to infity loop.

No it won't. The second parameter is whether you want it to initiate a reload. I specifically mentioned above that I use this to avoid an infinite loop.

I think the best idea for this purpose is to use setGridParam to change the sortname parameter and sortorder one.

Been there, tried that. setGridParam doesn't initiate any visual change to the column headers, which is what I'm trying to solve.

The idea to call sortGrid in loadComplete event is very dangerous. You will go to infity loop.

The reason for this is that sorGrid call again populate . When you populate you call loadComplete, which call again sortGrid and so on.

I think the best idea for this purpose is to use setGridParam to change the sortname parameter and sortorder one.

Regards

Problem #1:

My columns can vary from load to load so I hide/show them accordingly, but also adjust the sorting to a column that's valid on the backend. So if the previously sorted column no longer applies, a new one is chosen. However, jqGrid doesn't look for sorting variables in responses for the column header visuals to update.

Solution:

Within loadComplete I do: grid.jqGrid('sortGrid', data.sortBy, false, data.sortOrder.toLowerCase());

Obviously I don't want to unnecessarily loop things, so a reload isn't performed as part of this command.

Problem #2 (and bug):

Now what's happening is that the typical pagination controls aren't working. It won't advance beyond page 2. If I had to guess I'd say that the sortGrid method causes an internal page variable to reset to page 1. So while the visual still shows page 2, an attempt to move forward one page or backwards doesn't work because it thinks it's on page 1 already.

Thus, these work:

• Manually entering a page number / hitting enter
• Using the arrow control to go directly to the last page

And these don't:

• Incrementing up one page
• Decrementing down one page
• Going directly to the first page

All those behaviors make sense if you assume the logic thinks it's already on page one, which I'd put forth is the bug.