It all depends where you put this line of code. It is recommended to to this after calling the filterToolbar method.
Another solution of your problem is maybe to use defaultValue in colModel searchoptions. See docs.

Regards

var control = $("#gs_ColumnId", "#gridId");
console.log(control);
control.val('desired data');

I'm positive the IDs are spelled and capitalized correctly. When I run that, control contains zero selected objects.

 

Do you happen to know in what version this functionality was added? We're still on version 4.3.2 due to the possibility of breaking changes.

Sorry I put a wrong code. try this:

where grid1 and grid2 are your grid id.

I missed "#" in my previous post

How you set this in your code?

Kind Regards

 

2. I assure you that the jsonmap property works quite well for the server-to-page data flow.

1. You can solve this problem if you use

$("gs_EmpNo", "#grid1").val(...);
$("gs_EmpNo", "#grid2").val(...);

to differentiate the values,

2. This is not correct - the search try first to use the INDEX property and if it is not found it uses the NAME one.
So you can set the index to post the correct name to database.

Regards

The first problem is that while the grids themselves uniquely identify their components, the search toolbar does not. Suppose you have two simple grids for displaying lists of sales orders and user notifications respectively:

colmodel = [{label: "Sales Order ID", name: "SoId", index: "SoId", sortable: true, key: true},
            {label: "Sold By", name: "EmpNo", index: "EmpNo", sortable: true},
            {label: "Bought By", name: "CustNo", index: "CustNo", sortable: true}]

colmodel = [{label: "Notification ID", name: "NoteId", index: "NoteId", sortable: true, key: true},
            {label: "User", name: "EmpNo", index: "EmpNo", sortable: true},
            {label: "Message", name: "Msg", index: "Msg", sortable: true}]

When the HTML for the page is generated, you will see that the grid rows and cells are uniquely named in the format "gridGridName_ColumnName". No problem. However, the filter bars each end up containing id="gs_EmpNo". If we wanted to, for example, default the notification grid to display only the current user's notifications, setting the filter field's value by ID will end up populating the EmpNo field of both grids. Is this a known bug? Is there a workaround?

 

The second problem is related to our attempt to work around this. We can use jsonmap to ensure each field is uniquely named:

colmodel = [{label: "Sales Order ID", jsonmap: "SoId", name: "SoId", index: "SoId", sortable: true, key: true},
            {label: "Sold By", jsonmap: "EmpNo", name: "SoEmpNo", index: "SoEmpNo", sortable: true},
            {label: "Bought By", jsonmap: "CustNo", name: "SoCustNo", index: "SoCustNo", sortable: true}]

and so on. However, while this populates the grid correctly when there is no filter, the filtering request uses the name property rather than jsonmap. So the database ends up trying to filter by a field called "SoEmpNo", and promptly throws an exception because that doesn't exist. Is there a grid property we should be using to make it send the correct name back in the filter request, or something?

 

Thank you!