jQuery Grid Plugin - jqGrid - Topic: filtertoolbar with custom colModel searchoptions.sopt

ChrisXa on filtertoolbar with custom colModel searchoptions.sopt

Tue, 03 Jan 2012 13:06:53 +0200

I still think it's a bug. Of course, there should be a separate way to set search options for the filter toolbar. But as long as this is not possible, I expect the filter toolbar (just as I expect any other search input) to use the default search options.

OlegK on filtertoolbar with custom colModel searchoptions.sopt

Mon, 02 Jan 2012 13:24:52 +0200

It's important feature and not a bug. The defaultSearch option of filterToolbar method set default options for all columns. It makes problems. Let us you have colum with select having "equal" and "not equal" option. If you would use defaultSearch:'cn' option the row having either "equal" or "not equal" would be filtered because "not equal" contains "equal". To solve the problem one should include searchoption having 'eq' on the first place.

It is not the only example where one need specify the operation used for specified column intead of defaultSearch option of filterToolbar method used as the default searching operation for all other columns.

Best regards
Oleg

ChrisXa on filtertoolbar with custom colModel searchoptions.sopt

Mon, 02 Jan 2012 10:36:29 +0200

Bug still exists in 4.3.1.

corux on filtertoolbar with custom colModel searchoptions.sopt

Tue, 04 Oct 2011 12:25:29 +0300

Hi there,

I encountered an unexpected behaviour when using the jqGrid 4.1.2 filtertoolbar with colModel definitions that contained a custom set of searchoptions (sopt). The filtertoolbar search is always using the first of the defined custom searchoptions, disregarding the defaultSearch value set for the filtertoolbar.

Sample colModel definition:

colModel: [
   name: 'Name',
   index: 'Name',
   searchoptions: {
      sopt: ['eq', 'ne', 'bw', 'cn'],
   }
]

With this colModel, the search is always using the operator "eq".

I was expecting following behaviour: if the custom searchoptions contains the defaultSearch value specified by the filtertoolbar, use the default; otherwise use the first of the custom searchoptions.

Following change fixes the problem (jqGrid 4.1.2, Line 3473):

so = (this.searchoptions && this.searchoptions.sopt && (!p.defaultSearch || $.inArray(p.defaultSearch, this.searchoptions.sopt) == -1))
      ? this.searchoptions.sopt[0]
      : p.defaultSearch;

regards,

Tobias