Search

Have you considered licensing Editor? That has that functionality included. Colin

If you're just adding the rows to the DOM, you'll need to call rows().invalidate() to tell DataTables to rescan the table. Alternatively, use row.add() to add the row to the table. If that doesn't help, as rf1234 said, we'll need to see the code - a test case that replicates the issue will ensure you'll get a quick and accurate response. Information on how to create a test case (if you aren't able to link to the page you are working on) is available here. Cheers, Colin

By default, stateSave just saves the data into localStorage, and expects the table to be the same when it's reloaded. If it is changing, or if you want user specific saving, then you would need to use stateSaveCallback and stateLoadCallback to do deal with that. Colin

We're happy to take a look, but as per the forum rules, please link to a test case - a test case that replicates the issue will ensure you'll get a quick and accurate response. Information on how to create a test case (if you aren't able to link to the page you are working on) is available here. Cheers, Colin

Ah ha again. I think the issue was I wasn't properly fetching the draw param Now it's working without the increment thing.

The RowsGroup plugin is not apart of Datatables. I'm not familiar with how it works and how it would affect the rows. But I can see where Datatables would still count the "merged" rows as two since they are two tr in the table. You probably will need contact the developer of RowsGroup for your question. Or maybe the Datatables RowGroup extension will do what you want. Kevin

Hi kthorngren, kconrad and Colin Many thanks to each of you. @kthorngren, I had already consulted the https://datatables.net/examples/styling/bootstrap4.html link, and I opted for a radical solution, and by cleaning the code severely, I found a unclosed tag ... it only remains to hope that this is due to an unfortunate copy / paste.... Anyway, many many thanks again to each of you for your help

Hi @DW71 , The Select extension would be able to help achieve that. In this example here, the columns that wouldn't fit in the display are automatically shown. You can change the layout with responsive.details.renderer, see example here, and this could just make additional rows in the table to give those three rows you're after. With Responsive , you would get different results with different sized displays, but that could be managed by putting the table within a container. Hope that helps, Cheers, Colin

Problem solved, wrong event name been used.

Hi @055055 , We're happy to take a look, but as per the forum rules, please link to a test case - a test case that replicates the issue will ensure you'll get a quick and accurate response. Information on how to create a test case (if you aren't able to link to the page you are working on) is available here. Cheers, Colin