Search

This option is deprecated from version 2.0.0+. It was replaced by searchPanes.preSelect which allowed the order that the selections were made in to be defined. This allowed preselecting to become compatible with searchPanes.cascadePanes As standard, SearchPanes will not pre-select any values in any of the panes. If any of the elements in the array held in columns.searchPanes.preSelect are present in the pane then they will be pre-selected. Note: Before version 2.0.0, where this option was deprecated, columns.searchPanes.preSelect was not supported with searchPanes.cascadePanes. This was because in order to have the cascade operate as expected the selections had to be made in the correct order. It is however now possible in versions after 2.0.0 using searchPanes.preSelect

columns.searchPanes.orthogonal is used to create a custom rendering function. By setting its value to a string it tells SearchPanes how to display and filter on the data it is provided from the DataTable. SearchPanes uses rendering when populating the table and as standard will render the display value using the columns.searchPanes.orthogonal.display property and will identify the value to use while filtering by rendering on the columns.searchPanes.orthogonal.filter value. columns.searchPanes.orthogonal is normally only defined as a string when dealing with arrays. By setting the render object to the following { render: { _: '[, ].name', sp: '[].name' } } and columns.searchPanes.orthogonal to 'sp', the original array will be displayed in the dataTable as a list separated by ', ', where as in the SearchPane each individual element will be displayed. It is then possible to search by individual element rather than the entire array combination.

As standard, SearchPanes will be displayed with the ordering buttons included in the interface. However if the value of columns.searchPanes.orderable is set to false then the ordering buttons will no longer be displayed. The ordering buttons can be hidden for all of the panes by making use of searchPanes.orderable.

As standard, SearchPanes will not add any custom options to the panes. When columns.searchPanes.options.value is a function, this function is used when searching the table. The function receives the following parameters. rowData - the data from the current row being compared as an array with one element from each column rowIdx - the index of the row currently being compared The function's context is an API instance of the host DataTable. This means that from within the custom search functions it is possible to call API methods, such as this.rows().data(). The function must return true if that row is to be included in the search results and false if it is not. This is useful when you want to add an option to search for which isn't a value in the table. For example, "Countries in Europe", or, "Cities which aren't Edinburgh", or age ranges.

As standard, SearchPanes will set the names of the pane based on the title of the corresponding column. This option customises that name. The order of the panes is then set using the searchPanes.order option.

This option is deprecated from version 1.2.1+. It was replaced by columns.searchPanes.viewCount to maintain consistency with searchPanes.viewTotal. For now this option can still be used, but it will be removed in the future. As standard, SearchPanes will be displayed with the count column included in the table. However if the value of columns.searchPanes.hideCount is set to true then the count column won't be displayed. The count column can be hidden for all of the panes by making use of searchPanes.hideCount.

As standard, SearchPanes will set the headers of the pane based on the title of the corresponding column. This option customises that text in the pane's header.

Empty cells will be represented in the panes by the option columns.searchPanes.emptyMessage for that specific column. This is useful as it's a more user-friendly way than just having a blank cell. The value is passed through the i18n() function. Note, this value is only used if searchPanes.i18n.emptyMessage and language.searchPanes.emptyMessage are undefined. If this is the case then this value will over-ride the global value searchPanes.emptyMessage for this specific column.

As standard, SearchPanes will overwrite the options for that column defined by the SearchPanes code with the options defined in columns.searchPanes.dtOpts. As Standard SearchPanes internal DataTable has a layout property set to show only the table, if you are added paging or something visual then you must also modify the layout option. This functionality is useful as it allows all of the standard DataTables options and API methods to be available to all of the the panes, either globally or individually. All of the panes can be altered by using the searchPanes.dtOpts option.

As standard, SearchPanes will be displayed with the control buttons included in the interface and searching will be enabled. However if the value of columns.searchPanes.controls is set to false then the control buttons will no longer be displayed and searching will be disabled. The control buttons can be hidden and searching disabled for all of the panes by making use of searchPanes.controls.

page 2, the title columns do not align with

highlight some of the columns as re-orderable when they're

fit), Responsive starts hiding columns before the cells have

made up of 78 columns, but I only ever

even when there are columns that could be made

and nothing disappears when columns are hidden/re-shown, and identical

the contents from multiple columns, and concatenate them into

to highlight in hidden columns? I would like to

Is there a way to limit the multi column ordering to only 2 columns at a time? On the client side, I want to allow users to sort up to 2 columns at a time.

rowgroup keeping ALL the columns (instead a only one