Columnfilter requires column to be searchable: why?

  • Resolved mikeprince

    (@mikeprince)


    4 years, 7 months ago

    It looks like column filters require the column to be searchable. If it isn’t they return no results. I don’t see why this has to be the case.

    On my example page to demonstrate this, I have made the Status column not searchable using "columnDefs": [ { "searchable": false, "targets": [ 4 ] } ] The similar column IUCN is searchable. The dropdown column filter on Status does not work, but IUCN does.

    The problem with it being searchable comes from the actual search field. If I search for the string ‘lc’ for example, it is actually found many times in the IUCN column and therefore confuses the results.

    Logically column filters should not need to be searchable: it is a valid use case to be able to use a dropdown filter but not a text search on the same column.

    Am I missing something here?

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Columnfilter requires column to be searchable: why?’ is closed to new replies.