Search

This object sets the text for the condition names in the condition select element. The defaults for each language option is listed below. equals: 'Equals' not: 'Not' startsWith: 'Starts With' notStartsWith: 'Does Not Start With' contains: 'Contains' notContains: 'Does Not Contain' endsWith: 'Ends With' notEndsWith: 'Does Not End With' empty: 'Empty' notEmpty: 'Not Empty'

This object sets the text for the condition names in the condition select element. The defaults for each language option is listed below. between: 'Between' empty: 'Empty' equals: 'Equals' gt: 'Greater Than' gte: 'Greater Than Equal To' lt: 'Less Than' lte: 'Less Than Equal To' not: 'Not' notBetween: 'Not Between' notEmpty: 'Not Empty'

This object sets the text for the condition names in the condition select element. The defaults for each language option is listed below. after: 'After' before: 'Before' between: 'Between' empty: 'Empty' equals: 'Equals' not: 'Not' notBetween: 'Not Between' notEmpty: 'Not Empty'

This object sets the text for the condition names in the condition select element. The defaults for each language option is listed below. contains: 'Contains' empty: 'Empty' equals: 'Equals' not: 'Not' notEmpty: 'Not Empty' without: 'Without'

This will set the placeholder text for the condition select element, by default this is 'Condition'. This dom element is available in custom conditions and plugins also.

form to use when searching a dataset. When using searchBuilder.preDefined searches, this value is also

This option allows for a limit to be set on how deep sub groups can be placed from the top level. The top level is considered the first level. Setting a searchBuilder.depthLimit of 2 would allow for criteria to be indented by 1 level as this would then be at the second level - the limit. As default the limit is false, meaning that criteria can be indented as far as desired. Take a look at this example to see this in action.

This is useful as it allows restrictions to be made on which data points can be filtered on. For tables with a large amount of columns, this prevents having a large set of options within the select element.

This example shows how to use the saveState.columns.visible configuration option (see stateRestoreConfig#saveState) to disable the saving of the table's current column visibility by setting the initialisation option to false. The default value is true meaning that the visibility of the columns will be saved.

This is the section for showing the key configuration options that are available with SearchPanes. This includes showing sub-totals, cascading the panes, selecting which panes to show or hide and pre-selecting rows to name a few.

se in the first search pane that for example

the strings in a search, along with any other

You are using this search: column .search(val ? '^' + val + '$' : '', true,

In the search plugin you can use any supported Javascript method like regex search(). Kevin

When I think about it, this should not be possible as the search panes only contains unique values. There is nothing to group on. Right?

Thanks! Is it possible to somehow target an indiviual search pane?

Because that's a dynamic element, you need to get the val() of the select during the search. This example here demonstrates input elements, the same applies for select, Colin

One additional thing - worth noting that since you are using server-side processing, it is only possible to search in ISO8601 format.

believe the API's, like search() is available in 1.9.

the users, and just search on "ACV ACY", and