Hi, I have identified a bug that I have spent some time investigating. Here are the steps to reproduce it:
Configure a table where a query is used to load data.
Drag an input field onto the screen and configure "fuzzy search" to use the input field for searching within the table data.
Now, configure server-side pagination and modify the query to enable server-side pagination. (Note: This will remove the "fuzzy search" settings, but they will remain set in the background.)
Adjust the query to use the input field for filtering.
At this point, the filtering does not work even though the query is correctly configured. This is because the "fuzzy search" settings have disappeared (due to enabling server-side pagination) but are still retained in the background. To prevent this, you need to first disable server-side pagination to adjust the "fuzzy search" settings again (remove the link with the input field). Then, you can re-enable server-side pagination, and the filtering will work correctly.
Thanks for reporting this Dennis! You're right that the table should clear or ignore any existing "Search" settings when server-side pagination is turned on. I've filed this as a bug!
For now, you're correct that turning SSP off, clearing the search value, and re-enabling it should fix the issue and the Table should filter as intended.
Hey, @AnnaW. I'm confused. Does this mean that Search functions can be enabled for SSPs? I can't get my fuzzy searches to work now that I've enabled SSP.
I made some progress on solving this issue by creating a search function for my solution.
I divided types of searches I need to do and created different server queries ( I'm using Firebase ) My approach is not to rely on table.selectedRow.whateverData so whatever data I pulled from server based on the query was saved in a global variable which I can reference to load the data in different components.
This is the only way I could get it to work. I hope it makes sense.
Fuzzy search does not work with server-side pagination. However, you can implement search and filter functionality for a specific field using a Dynamic JavaScript Query.
Here’s a screenshot demonstrating the implementation:
It's definitely tricky with server side pagination.
Since the built-in filters aren't fully compatible, you could create your own filter options & apply them to your query (note for SQL, the filters need to be applied to the total count query & the table query):
