[Feature]: configuration for default Table widget filter

[hilton]

Is there an existing issue for this?

• I have searched the existing issues

Summary

Add a way to set the initial state of the Table widget filter, so the app can set filters based on interaction elsewhere. Otherwise, either the user has to set the filter UI manually, every time, or the app can filter the source data it gives the table, but then has to duplicate the filter UI to manipulate that source data filter.

Why should this be worked on?

The table widget’s filter is not currently integrated with the rest of Appsmith, which means that it can’t be used for use cases that require any kind of predefined filter.

Our use case is web shop orders. We have a customer details view, and a table of all/recent orders. We want the customer details view to include a Customer orders button that navigates to the table of orders, and filters the table by customer ID.

We can do that by setting the Customer orders button to store the current user ID, and then use that to filter the orders data, but then the Orders page only shows data for the last-viewed customer. To fix this, we need to add a Show all orders button to the table, which is ugly, and duplicates filter functionality.

What’s one option for how this might work? While the table has a Default search text property, there’s no similar Default search filter configuration. Even if limited to a single attribute/operator/value, that would be valuable.

[sam-bercovici]

There are three different use cases:

1. When setting a filter on a table and navigating to another page, when returning back, the filter is cleared. I would like an option to persist the filter in the store
2. Preparing predefined list of filters so a user can choose between them
3. Navigating from another page and setting the filter according to some values selected in the source page