It’s a bug. One needs include return; line after the line of jqGrid code (see here). You can get the fixed version of jquery.jqGrid.src.js here.

Best regards
Oleg

Hi,

usage of demos simplify all. The reason of the problem with sending wrong idCity – the rowids of the grid will be wrong assigned. It’s a bug in jqGrid. The bug exists in combination of the usage of arrays of strings as the input value of row like [“13570″,”Some name 1″,”Australia”] and the usage of key:true property in colModel. I will post later to github my suggestion how to fix the problem. As the workaround I suggest you to add jsonReader : {id: 0} option and remove key:true property from the first column definition.

See http://jsfiddle.net/OlegKi/d26hzhu6/3/

About the problem with the requirement to post idCity=3 instead of the text “Australia” I wrote you two times before. You used wrong configuration which worked in old versions of jqGrid, but the but are fixed some years ago (probably in the version 4.4.5). So you should decide whether you want that jqGrid hold values like 1,2,3 in idCity column (and displays still the texts “London”, “Washington”, “Australia”) or you use the texts “London”, “Washington”, “Australia” in the data. In the first case you the communication with the server will be in ids 1,2,3, but the values have to be used in both input of grid and the output. Exactly the example I used in the modified demo. Alternatively you can fill jqGrid with the data like “London”, “Washington”, “Australia”, but exactly the same data will be send to the server during editing.

You still can use serializeEditData to remap any standard values like “London”, “Washington”, “Australia” to 1,2,3 or on the contrary, but I don’t recommend you to do so because I personally find such kind on communication transfer non-consequent.

Best regards
Oleg

To fix the problem one have to debug the code. So one needs to have the working demo which uses uncompressed version of jqGrid jquery.jqGrid.src.js (instead of jquery.jqGrid.min.js). If one can see that wrong information will be posted to the server that one don’t need and server part to debug such demo. So please prepare always a working demo if you report the bug.

About the first issue which you report all sounds very strange. You write about “the id’s of the combos instead of the text“. So you use probably select with options having different value and the text. It seems me wrong if you use edittype:’select’ and not uses formatter:’select’. One uses different values and texts in select options only in the case that one fill the data with ids (values), but one want to display the texts for the user. formatter:’select’ do that. The only disadvantage of the approach is that the formatter have to know the mapping between ids and the texts during filling of the grid. One can’t make an additional asynchronous call to the server. So one uses formatter:’select’ with editoptions.value instead of usage of editoptions.dataUrl. If one need still build dynamic values of editoptions.value one can set it inside of beforeProcessing callback. See the answer for more details.

About the problem with the date format you should try to use reformatAfterEdit: true option of formatter: “date”.

Best regards
Oleg

Hi Greg,

I created the pull request based on your bug report.

Best regards
Oleg

I wanted just add that

seems be better as

Best regards
Oleg

Sorry, but it seems to me that you didn’t read the referenced answer. I repeat: I suggest to create navGrid with all buttons which you could need make visible later. Then you hide unneeded buttons directly after creating and show it later when the button will be needed. The demo from the answer demonstrates how buttons from navGrid can be shown or hidden. 

Regards
Oleg

Hi Vignesh,

look at the answer and this one in which included the corresponding demos. The idea is very easy: one can create all buttons and hide currently unneeded buttons. Later one can make some buttons visible depend on which row is selected. Alternatively on can disable/enable buttons instead of showing/hiding.

Best regards
Oleg