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.

take over the global search input's keyup event and

for a specific columns search table.column( 1 ).search( content

You can over-ride the existing search control and disable the smart search() - this means that the characters must be sequential. That gives you something like this, Colin

event on the DataTable search element. If that doesn't

It just needs some logic to determine if there is a search string in place - see updated example here: http://live.datatables.net/mowobugu/4/edit Colin

you don't want the search input and use that

some issues with the search. 'I tried finding this

to be the column search select options oren't updated

6. For the Office search use London for an

In this case the search plugin wont help as