Guriddo » Topic: stype=”select” search field name is wrong

stype=”select” search field name is wrong

Guriddo
stype=”select” search field name is wrong

This topic has 11 replies, 5 voices, and was last updated 16 years, 5 months ago by tony.

Creator

Topic
November 16, 2009 at 10:54 pm #74675

Wan
Participant

grid.formedit.js

line:52

soptions = $.extend({},{text: colNames,value: v.index || v.name},this.searchoptions),

Should be:

soptions = $.extend({},this.searchoptions,{text: colNames,value: v.index || v.name}),

Because if the stype==”select” then searchoptions may contain the value atrribute.

And we will buildOption based on the fields.value which now is an object. That will make the search filter looks like this:

{“groupOp”%3A”AND”%2C”rules”%3A[{“field”%3A”[Object+Object]“%2C”op”%3A”eq”%2C”data”%3A”card”}]}
Creator

Topic

Viewing 11 replies - 1 through 11 (of 11 total)

Author

Replies

November 16, 2009 at 11:20 pm #90699

tony

Keymaster

Hello,

Aha, Thanks. Will be fixed.

Regards

Tony

November 17, 2009 at 12:51 am #90723

Wan

Participant

I edited the src file, it seems work, but if I edit the minifyed js file directly, the options will display “undefined”. Anything wrong?

When & where can I get the fixed release?

Thanks a lot!

November 17, 2009 at 12:52 am #90724

tony

Keymaster

Hello,

If you have ant istalled you can make a min file easy

Regards

November 17, 2009 at 1:05 am #90726

Wan

Participant

Any docs about it here?

the minifyed file is not so hard to read, I found this one:

soptions=b.extend({},{text:v[w],value:j.index||j.name},this.searchoptions)

& change to:

soptions=b.extend({},this.searchoptions,{text:v[w],value:j.index||j.name})

then the options will not be displayed.

November 17, 2009 at 1:14 pm #90763

magic_pie4

Participant

I believe this is related due to the topic title, but I don't understand the solution.

I have a grid with a column setup as this:

{name:&#039;merch_id&#039;,index:&#039;merch_id&#039;,width:150, align:&#039;center&#039;,editable: true, stype:&#039;select&#039;, searchoptions:{value:"00000003:ABC Company;00000004:XYZ Company", sopt:[&#039;cn&#039;,&#039;nc&#039;]}, formatter:&#039;select&#039;, edittype:"select", editoptions:{value: "00000003:ABC Company;00000004:XYZ Company"}},<br />

1	{name:'merch_id',index:'merch_id',width:150, align:'center',editable: true, stype:'select', searchoptions:{value:"00000003:ABC Company;00000004:XYZ Company", sopt:['cn','nc']}, formatter:'select', edittype:"select", editoptions:{value: "00000003:ABC Company;00000004:XYZ Company"}},<br />

When you bring up the search dialog, it displays the items correctly as a dropdown and you can select them, etc. Once you submit this however, it sends the following parms:

1	When you bring up the search dialog, it displays the items correctly as a dropdown and you can select them, etc. Once you submit this however, it sends the following parms:

<tr><td class="netInfoParamName">_search</td><td class="netInfoParamValue"><pre>true

1	<tr><td class="netInfoParamName">_search</td><td class="netInfoParamValue"><pre>true

1258484858633

1	1258484858633

oper

getdata

getdata

page

1

rows

10

searchField

<span style="color: #ff0000">00000003:ABC Company;00000004:XYZ Company</span>

1	<span style="color: #ff0000">00000003:ABC Company;00000004:XYZ Company</span>

searchOper

cn

searchString

00000004

00000004

sidx

list_name

list_name

sord

asc

asc

<br />Note the searchString is correct (from the one I selected), but the searchField should be populated with merch_id.

1	<br />Note the searchString is correct (from the one I selected), but the searchField should be populated with merch_id.

November 17, 2009 at 7:51 pm #90772

Wan

Participant

I'm not so familiar with params you listed, so I guess you are not using the 3.6 release.

Actually, if you are using the version 3.6,you will notice a param called:filters. That's the key/value what we are talking about.

November 18, 2009 at 7:18 am #90785

tony

Keymaster

Hello,

@magic_pie4 – In case of single search that are the parameters. Please refer to docs in order to see the difference.

@ssss…s – I have made the changes in GitHub.

Tony

November 18, 2009 at 8:37 am #90795

Klaus Pesendorfer

Participant

I've noticed similar problems with the definition of the value-attribute for stype:select in the search-/editoptions and my table search still does not work with the patch (of changing the order of the soptions-extend) mentioned above!

I solved the problem the following way, which in my option is not really a clean solution:

… stype: 'select', editoptions:{value:{'yes':'yes','no':'no'}}

November 18, 2009 at 8:39 am #90796

magic_pie4

Participant

I am doing a single search. The problem I'm having is when I use the

stype:'select', searchoptions:{value:”0003:ABC Company;0004:XYZCompany”}

November 19, 2009 at 4:22 am #90820

tony

Keymaster

Hello,

@Klaus – Thanks for this and the recommendation. I will look on this right now.

@magic_pie4 – Thanks for this. Will test with your options and let you know about the result

Best Regards

Tony

November 19, 2009 at 1:28 pm #90778

blejzu

Participant

I'm not sure if it's related to this bug, but Advanced Search example in jqGrid demo is broken. After choosing “Tax” field you get undefined instead of tax values.

Author

Replies

Viewing 11 replies - 1 through 11 (of 11 total)

The forum ‘Bugs’ is closed to new topics and replies.

Stay connected with us in your favorite flavor!

stype=”select” search field name is wrong

Search Forum

Recent Replies

Forum Statistics

UserOnline