jQuery Grid Plugin - jqGrid - Topic: prmNames bug when set to null ?

aNt1X on prmNames bug when set to null ?

Wed, 03 Apr 2013 12:50:20 +0300

Ok, now i understand.

I would suggest you to update the documentation and specify what parameters can be set to null.

Thank you!

tony on prmNames bug when set to null ?

Wed, 03 Apr 2013 11:58:12 +0300

Hello,

Some parameters can not be omited. Since they are very basic for us we cannot ommit them.

You always can set some name which you will never use.

The parameter that are checked for nuls are:

search, nd , rows , page, sort , order ,rowTotal , totalrows

Regards

aNt1X on prmNames bug when set to null ?

Wed, 03 Apr 2013 10:51:52 +0300

Hi,

folllowing the documentatinon at /jqgridwiki/doku.php?id=wiki:options;..038;hellip;..ki:options

i'm setting prmNames to the following:

prmNames: { id: '_id', oper: null }

now, with fiddler, i see that in my raw request i have:

{ … "null":"edit","_id":"052eb5f5-bc9b-e211-a143-3a4d1aec23f3″ … }

you can see that "_id" has been applied correctly, but i was expecting that setting "oper" to null it would omit the parameter; instead, it is setting the string "null" instead of the "oper" string …

but, according to the documentation, "When some parameter is set to null, it will be not sent to the server. For example if we set

prmNames: {nd:null}

the

parameter will not be sent to the server."

Please note that this append to the "_id" parameter; i would like to set it to null, because i already have my "Id" parameter inside my fields, and i would like to omit the default one.

And also, could these parameters be different from action to action ?

Thank you for your work!

Best regards