Search

that they set. On initialisation SearchBuilder analyses the DataTable

ordering rows. The example initialisation of the RowGroup extension

very basic pie chart initialisation is shown below: var

To use the scrollToTop plug-in, first include its JavaScript on your page: JS Then enable it by specifying the scrollToTop option in your DataTables initialisation: $('#myTable').DataTable({ scrollToTop: true });

For the DataTables initialisation we need to define

it at the table initialisation stage, then place the

On initialisation of the DataTable, the

DOM / Array sourced data Initialisation: $('#myTable').DataTable( { rowGroup: { // Group by

The DataTable initialisation is equally as simple

option to your DataTables initialisation: $('#example').DataTable( { pageResize: true } ); Option

Do you have an async process that might be getting an instance of the API, ie, $('#myTable').DataTable();? If this executes before you init Datatables due to debugging then you will see the error. Kevin

Hi @Nite01 , The init() api method might do what you want here. It returns the object that was used to initialise the table so you can check that. Thanks, Sandy

Try moving the buttons init code into the document.ready()

the last line of initComplete so it executes after the initial table draw() but before

First I would temporarily remove the Datatables init code to see how long the page takes to load without Datatables. This should help to determine if Datatables rendering is the problem. Kevin

that uses the Constructor init. It uses fixedColumns().left() to

the file is the init per the example: $(document).ready(function

element.status = 'waiting'; }); Then in init complete I fetch the status using ajax initComplete: function () { data.forEach((element) => { var

problem is with the initComplete code you pasted. Its

assigned to the Datatables init code is not available in initComplete. Sounds like you have