Search

myTable').DataTable( { responsive: true, columnDefs: [ { responsivePriority: 1, targets: 0 }, { responsivePriority:

Responsive will automatically remove columns from the right-hand-side of the table when a table is too wide for a given display. Although this is a useful default, you may want to control the order in which columns are hidden. This parameter provides that ability by setting a visibility priority order. The value given will set the column's visibility priority with a lower number representing a higher priority in terms of staying visible in the table. For example a column with a priority of 2 will be removed from the display before a column with priority 1, regardless of the order that they appear in the table. This can be particularly useful for cases where you wish to keep the right-hand column(s) visible if they contain action buttons or other important information. The column priority can also be defined by a data-priority attribute on the column's header cell (for example <th data-priority="1">First name</th>). If both a data-priority attribute and a columns.responsivePriority value has been set for a single column, the columns.responsivePriority value will always be used.

your answer. Your code: { responsivePriority: 1, targets: 0 }, { responsivePriority:

field targeted as a responsivePriority, but I only want

when I try to use responsivePriority it showing below error 'responsivePriority' does not exist in type 'ColumnDefsSettings' Versions "datatables.net-dt": "^1.10.22" "datatables.net-responsive-dt": "^2.2.6"

title: "Número de emplazamientos", responsivePriority: 3, "width": "25vw", orderable: true }, {title : 'Capas', responsivePriority:4, "width": "25vw", orderable: true},

how to overwrite the responsivePriority order hiding a column

the array). I tried { responsivePriority: 1, targets: 1 } in

the responsive DT with responsivePriority. The problem is that

Hi @mattct , I've tried this on drawCallback, which seems to achieve the desired behaviour. How does this look rather than on initComplete? drawCallback is called every time the table is drawn (paged, ordered or searched), initComplete is only called once when the data is loaded. So, your code above looks right for your issue. I think I'm right in assuming I can remove the above $('#dt_basic').on('order.dt', function (){... function as drawCallback enables the same thing? Yep. The order.dt wouldn't have an effect if you paged or searched, so the drawCallback is the correct place to go there. Cheers, Colin

orderable: false, }, { data: "LK_KLANTNR", responsivePriority: 2, }, { data: "LK_NAAM", responsivePriority:

null, defaultContent: "", orderable: false, responsivePriority: 1 }, { // 1 title: "Venditore",