Request for adding the "persistence" and "persistence_type" arguments

[kn5-copilot]

Hello @mwouts,
I hope your are doing well.

I am building a rather sizable multi page app, where Itables is used on most pages.

Currently when the user sets filters on an Itable on page A, navigates to page B and then comes back to page A, the filters and other modifications done to the Itable on page A are lost.

So far I have tried to save the Itable in the dcc store. This did not work entirely. The data is kept in memory, but apparently not the filter operations.

Usually I get around the persistency issue by setting the persistence=True argument in the dash components directly, as described here:
https://dash.plotly.com/persistence

My change request is therefore the addition of those arguments to the Itable object and therefore the implementation of persistency of filter and modification operations, in a multipage setup.

Thank you very much for your effort.

[mwouts]

Hi @kn5-copilot , thank you for pointing at this! I will have a look.

In the meantime, can you try passing stateSave = True to your ITable object? See https://mwouts.github.io/itables/options/state_save.html for an example. It should preserve the filter, selected rows, etc.

Please note that the stateSave option comes directly from DataTables, meaning that you can also consult their documentation, for instance https://datatables.net/reference/option/stateSave.

[kn5-copilot]

Hi @mwouts, thank you for your quick reply!

I implemented your suggestion regarding stateSave = True. This seems to work. The filters are now preserved.

[mwouts]

Hi @mwouts, thank you for your quick reply!

I implemented your suggestion regarding stateSave = True. This seems to work. The filters are now preserved.

Oh great! Thanks for letting me know