Thanks for this. Yes we have tested the export, but not import.

Also will be fixed.

Thnaks again

Tony

I'm using the 3.6.4 version of the jqGrid and also need to do exports of grid config, store it, and then reimport it at some later point.

The bug was fixed for the export, but when importing, the filter does not come right, the url takes the filter as [Object+object].

I had to quote the whole filters json string in single quotes at lines 163 to 166

if(gprm.postData.filters != undefined) {
   ret=ret.replace(/filters":"/,'filters":\'');
   ret=ret.replace(/}]}"/,"}]}'");
}

Hope this helps!

Genny

I do not know which version do you use, but it is fixed in 3.6.4

http://github.com/tonytomov/jq.....8c8400b447

Best Regards

Tony

I am using the jqGridExport/Import functions and have come across a potential bug when using  postdata with setGridParam.

If I do a search with the grid and then hit the default reset/reload button on the pager, and then export my grid I get non-valid json in the form of:

...

"postData":{
            "_search":false,
            "nd":1266945818052,
            "rows":5000,
            "page":1,
            "sidx":"BLDRM",
            "sord":"asc",
            "filters":"
        },

...

as you can see there appears to be an unescaped quote for filters

BUT if i create my own reset button using the code below:

jQuery("#showBuildings").setGridParam(
                {
                    postData:
                    {
                        serialString : "status=1",
                        filters:null
                    },
                    page:1,
                    search:false
                }
            ).trigger("reloadGrid");

I am able to get the export to function as expected:

...

"postData":{
            "_search":false,
            "nd":1266945392829,
            "rows":5000,
            "page":1,
            "sidx":"BLDRM",
            "sord":"asc",
            "filters":null,
            "serialString":"status=1"
        },

...

Any attempt to use filter:'' or filter:"" will cause the export to produce invalid json, only null seems to produce valid results.

does this seem like a bug to you?

thanks

billy