Search

Yes. Use column().visible(). Just modify the example a bit to specify the column, like this: table.column( 2 ).visible( ! table.column( 2 ).visible() ); table.column( 3 ).visible( ! table.column( 3 ).visible() ); KEvin

Ohhh; brilliant! That also solves my column filtering issue. This is what I am now doing: "ajax":{ url : 'YouthMemberAdminListView', data : function (d){ d.ssAccountLevel = sessionStorage.getItem('ssAccountLevel'); d.ssAccountID = sessionStorage.getItem('ssAccountID'); d.ssArchived = sessionStorage.getItem('ssArchived'); d.ssGroupSection = sessionStorage.getItem('ssGroupSection'); d.filterSurname = filterSurname; d.filterFirstName = filterFirstName; d.filterBOB = filterBOB; d.filterGender = filterGender; d.filterNumber = filterNumber; d.filterStart = filterStart; d.filterInvested = filterInvested; d.filterNotBirthday = filterNotBirthday; }, With many thanks and kind regards, Glyn

There's a lot of mistakes in that fiddle - it's not running, plus you're only adding one column back into the table. Kevin's example from this thread may help - it's hiding rows with black cells. You could modify that for your use case. Colin

Use createdRow if the data is static or rowCallback if the data can change. The docs have some example code plus a running example here. Kevin

http://live.datatables.net/

thx Colin, I'll take a look...

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

Use createdCell or createdRow. If the data can change then use rowCallback instead. Kevin

That is correct and expected. We do not currently copy across the classes that were added externally. If that is something you want to do you'd need to use either a custom renderer, or probably easier, use responsive-display to modify the display elements when the details information is shown. Allan

I just want to add to this to help someone in the future. The method I mentioned of not defining the non-editable fields in the editor instance is not the correct way to go about it. There is the readonly field type which should be used instead. And if necessary, you can use fields.submit to prevent the field from being passed for update. Example: editor = new $.fn.dataTable.Editor( { table: "#example", fields: [ { label: "Name:", name: "name" }, { label: "Position:", name: "position" }, { label: "Office:", name: "office" }, { label: "Age:", name: "age" }, { label: "Start date:", name: "start_date", type: "datetime" }, { label: "Salary:", name: "salary", type: 'readonly', submit: false /* Optional */ } ], formOptions: { main: { scope: 'cell' // Allow multi-row editing with cell selection } } } );