Search

DataTables warning: Non-table node initialisation (). where is replaced with

Generally you don't need to know programmatically when a new Editor instance is created, since you use new DataTable.Editor(...); to create a new instance and any dependent code can follow. However, it can be useful to apply common actions, event handlers or even for testing to multiple Editor instances, and this event provides that ability. Note that unlike the other Editor events, do not listen for it on the Editor instance (since you don't know what that is!), but rather on the document element. The Editor instance that was created is passed in as the second parameter to the callback function.

Initialisation of the Editor instance

It can often be useful to know when your table has fully been initialised, data loaded and drawn, particularly when using an ajax data source. In such a case, the table will complete its initial run before the data has been loaded (Ajax is asynchronous after all!) so this callback is provided to let you know when the data is fully loaded. Additionally the callback is passed in the JSON data received from the server when Ajax loading data, which can be useful for configuring components connected to your table, for example Editor fields.

Select is an extension for DataTables that provides the end user with the ability to select table items (rows, columns and cells). It provides API methods and events to then be able to take action on those selected items. The examples in this section demonstrate how Select can be initialised and its various options.

This example shows how to initialise SearchPanes through the DataTable.SearchPanes constructor. Note that it is unlikely you'll ever need to do this, but it is included here for completeness.

This is the SearchBuilder extension for DataTables. It allows results to be filtered based on a user constructed arbitrarily complex query. This is done by creating criteria and sub groups, leading to a powerful interface for filtering data within your DataTable. Please see other examples for more detail.

This example shows how to initialise SearchBuilder using the API, rather than initialising within the config. This is done by making use of the constructor manually and retrieving the node using searchBuilder.container() before inserting it into the document.

The examples in this section demonstrate how RowGroup can be initialised in DataTables and how the options for the software can be configured.

a href="//datatables.net/reference/option/fixedHeader">initialisation option">fixedHeader option. This can

I've circled back to this a bit, and one of the things that I wound up doing was adding my own mechanism for adding buttons via a data-additional-buttons tag, along with a linkButton type. I'm probably reinventing the wheel a bit though, since I have my own custom button type list instead of exting the existing base button types. var customButtonTypes = { "linkButton":{ action:function ( e, dt, node, config ) {location=config.url;} } } var buttonConfig = []; if($(this).data("additionalButtons")){ var additionalButtonList = $(this).data("additionalButtons") for(var ii = 0; ii< additionalButtonList.length;ii++){ var btnConfig = additionalButtonList[ii] if(btnConfig.baseType !== null){ if(typeof(customButtonTypes[btnConfig.baseType]) === "object"){ jQuery.extend( btnConfig, customButtonTypes[btnConfig.baseType]) } else { if(typeof(console.log) === "function"){ console.log("unsupported Button type"); } } } buttonConfig.push(btnConfig); } } var datatablesConfig = { buttons: { buttons: buttonConfig, dom: { button: { className: 'btn' } } }, "drawCallback": function( settings ) { var api = new $.fn.dataTable.Api( settings ); var info = api.page.info(); var showExportButtons = false; try{ if(info.recordsDisplay > 0){ showExportButtons = true; } } catch (err){} if(showExportButtons){ api.buttons( '.buttons-html5' ).enable() } else { api.buttons( '.buttons-html5' ).disable() } } }; var table = $("#target").DataTable(datatablesConfig);

It's okey, i had to use option "editOnFocus". Thanks!

@kthorngren Kevin, I ended up going with your solution. It still feels a little like a workaround and I'm sure @allan would have a cleaner way to do it without having to build the entire table, render it and then remove, but this works. Thanks again for the idea.

Is it possible to select the first row automatically when the DataTable is initialized? dataTable.row(':eq(0)').select(); (row().select()). I want, that at least one row keeps selected. Not with Select's built in selection controls. However, you have two options: You could listen for deselect and if you find no rows are selected (dataTable.rows({selected:true}).any()), then reselect that row. Use your own click event listener and the API methods to select rows, rather than the built in options. Allan

Assuming you are using the Editor PHP libraries, this can be done with the Field::inst() constructor. The first parameter passed in is the database column name and the second is what is exposed in the JSON and what it expects from the client-side. The .NET libraries work the same way if you are using them. Allan

It sounds like you might want to use server-side processing. See this section of the manual for a description. Allan

I was able to get around it. Instead of table.columns(2).visible(false).table.draw(); to simply show the table I initialized it again with dataTable().fnSettings().aaSortingFixed and set the order I wanted.

Wow, it just takes a bit of reading the documentation :) I found cell/s/row/s.invalidate(). Will try that for now, and if that also fails for some reason, I'll resort to modifying the table manually with the api, disabling DerbyJS updates.

That looks like it should work okay. Can you please link to a test case showing the issue, or use the DataTables debugger, as per the forum rules. Allan

Currently no - there is no option to change the data property after initialisation. You would need to destroy the table and create a new one with the new options. Allan