Issue with setting filter state.

[adenisov8b]

In one of the tables, I am using manual control with server-side filtering. I have two columns. They are not displayed, so they are defined as follows:

{
  id: 'submittedCurrency',
  accessorKey: 'submittedCurrency',
},
{
  id: 'submittedValue',
  accessorKey: 'submittedValue',
},

I am trying to set a filter. Filters are passed by column ID. And all I need here just to set the filter state.

// works, actually here it just sets a value, but for testing - it sets the object
              currencyColumn?.setFilterValue({
                min: minValue,
                max: maxValue,
              });

// does not work, filter state for the column is not updated.
// if I set a string or array - it gets set. But the object does not, even though the same filter was recorded in the state for the previous column.
              amountColumn?.setFilterValue({
                min: minValue,
                max: maxValue,
              });
              
// works, filter state for the column is updated, but I need object
              amountColumn?.setFilterValue([minValue, maxValue]);

Do you have any ideas or suggestions?

[agammann]

If submittedValue contains a number in the first row, this matches v8's automatic filter selection: that column gets inNumberRange, whose value is an array [min, max]. Its autoRemove check sees an object { min, max } as having neither array endpoint and removes it from filter state. manualFiltering: true does not bypass that state cleanup.

For server filtering where you want to keep your object format, supply an explicit filter function on that column:

{
  id: 'submittedValue',
  accessorKey: 'submittedValue',
  filterFn: () => true,
},

Then your existing call keeps the object:

amountColumn?.setFilterValue({ min: minValue, max: maxValue });

The pass-through function is appropriate with manualFiltering: true, because the server supplies the filtered rows. If you later enable client filtering, replace it with a function that actually evaluates your object range.

I reproduced this using @tanstack/table-core 8.21.2 and 8.21.3: a string currency column retained the object, a numeric amount column removed it, and specifying the function above retained it. The built-in selection and state cleanup are in ColumnFiltering.ts; the filter function API describes custom functions and autoRemove.