You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 4, 2024. It is now read-only.
Hey folks,
We have a use case where we need to use backend filtering and sorting since our data in some columns is a mix of Strings and Ints. The given examples work well if we only need to filter and/or sort. The issue is we also need to keep row selections. The row selections break since the data is changing. Does anyone know how we can do this? Is there a work around? I though of using derived_virtual_data but it seems to be read only and would need us to set all the other derived properties too?
The text was updated successfully, but these errors were encountered:
In principle row IDs should make this work right, but I wouldn't be surprised if there are bugs. If you want to post a complete standalone example that reproduces a bug we can look into it.
Here is a MWE based on the "Backend Paging With Sorting" example from the docs. It just has row_selectable='multi' added to the table definition.
Also, #924 has a good MWE for some additional bugs with selected_rows when data is updated with a callback. The first example in #924 was fixed in #907, but I can verify that the other items are still issues.
Hey folks,
We have a use case where we need to use backend filtering and sorting since our data in some columns is a mix of Strings and Ints. The given examples work well if we only need to filter and/or sort. The issue is we also need to keep row selections. The row selections break since the data is changing. Does anyone know how we can do this? Is there a work around? I though of using derived_virtual_data but it seems to be read only and would need us to set all the other derived properties too?
The text was updated successfully, but these errors were encountered: