Keep/re-apply filters when data changes

Tags: #<Tag:0x00007efc64b0b5a0> #<Tag:0x00007efc64b0b438>
#1

Hello, I have a question.
So let’s say I have the following setup:

export default function MyComponent({data}) {
    const [filters, setFilters] = useState([]);

    const hotSettings = {
        ///..,
        filters: true,
        afterFilter: (conditionsStack) => {
            setFilters(conditionsStack[0].conditions);
        }
    }

    return (
      <HotTable data={data} settings={hotSettings} className="handsontable"
      ///...
      />
    );
}

Basically, the data that I display in the table, is passed as props in a component whose role is to only display the handsontable.
If I filter this table, I save the filters in the state, inside the afterFilter hook.

My question is, in this situation, how do I re-apply my saved filters when the data object changes?
I know I have to do something like this:

const tableFilters = formInstance.getPlugin('filters');
tableFilters.addCondition(filters);
tableFilters.filter();

But I am not sure where or when exactly.
Also, maybe my approach is wrong, if there is a better one, please let me know.

Thank you!

#2

Hi @vitorialipan

When you need to reapply the filters after changing the data set there are two options.

If you are just updating the data and want to keep the cells’ state you can use the updateData() method, and then afterUpdateData hook to reapply the filters conditions there.

If you don’t need to keep the cells’ state, then you can use the loadData() method and afterLoadData hook.

#3

Hello,

Thank you for the reply!
I think afterUpdateData was what I was looking for, but when I apply the filters inside this hook, I get the error:

Assertion failed: Expecting an unsigned number.

Do you have any idea in which context does this error appear? Like, in general, what is causing it?
Maybe this way I can understand where I went wrong with my code.

Thank you!

#4

Hi @vitorialipan

Can you please share a code demo with your implementation so I can check the error?

#5

I’m closing this thread due to the lack of a demo where we would be able to replicate the issue.

If you do not want to share the demo publicly @vitorialipan please contact us at support@handsontable.com

#6