Search

Take a look at this thread asking the same question. Kevin

Nope, sorry, that's not possible with DataTables, Colin

As Lapointe says you can insert HTML into a cell, so you could insert a Vue component and then have Vue dynamically register it, but I would very strongly suggest against it. You need to include some extra libraries from Vue to make that possible and the file size gets large. You'll also run into issues where both DataTables and Vue are trying to control the same DOM elements, which is just tears waiting to happen! Allan

For what you describe your server-side API would need to implement the client / server communication the Editor uses. We provide libraries for PHP, NodeJS and .NET to provide that functionality and write data back to a database. edit I forgot to address the point about the data not being shown in the Editor modal. Can you show me your full Javascript configuration please? Allan

I think because you're explicitly asking for a record, it's ignoring the fact that it's not on that page. Probably the easiest way would be to do something like this: if ( table.rows({page: 'current'}).ids().toArray().includes('id_1')){ $('#tiger').css('visibility','visible'); } See here, 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

The selector-modifier docs show that you can use none, applied or removed with search. Maybe you can use { search: 'applied' } then { search: 'removed' }? Kevin

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

@kthorngren thankyou. I have sorted it out now. Apparently, I was using same form template which was causing the error. As, soon as I removed one, it worked fine

The cog at the top-right should do it, but it might just be an admin thing! I'll close it now, Colin