Search

Its OK - Ive found another way around the problem but thanks for your help.... :-)

Thanks a lot Colin. It's nice that I can put it in columnDefs, now it's ok with all these defs : columnDefs: [ { visible: false, targets: [1, 15] }, { render: DataTable.render.number(' ', null, 0, null, ' €'), targets : [9, 10, 12] }, { searchPanes: { dtOpts: { order: [0, 'desc'] }}, targets: 15} ]

Here is a simple example: https://live.datatables.net/tefugala/1/edit It uses columns.className to assign a classname that is used as part of the event handler selector. Kevin

to just create the searches for your two columns.

That looks better, and at least not out of place. As long as it's a bit different so users aren't confused this should be ok :) Thank you

Correct, I assumed that the datatables do it, but I was wrong, thank yuo VERY much.

I changed the name of the object columns. It is working now. Problem solved. Thanks a lot.

I set the cascadePanes: false and is super fast now, but then the values don't get calculated when applying the filters. Just wondering, what does cascade actually does? apart from hiding the records from filters when not meeting filter criteria? I also disabled the viewTotal and that also speeds up filtering by ALOT, but how can I remove the calculated values then as they no longer update.

Hello, I had exactly the same problem. It was because of the CSS property "transition" inherited from my ResetCSS style sheet : * { transition: 0.4s; } Removing it solved the problem. Hope it can help.

This is a duplicate of your other thread. I've replied there. Allan