[Bug] Search in filter of tables only works if I'm on the same page as the item being searched

[Rishabhkaul]

While searching through a table, I am only able to filter for data on the page that I am on. So with pagination this becomes an issue.

Steps to reproduce the behaviour:

I've used the Applicant Tracker App to show case this issue, but this is a larger issue with Tables (since the same thing has happened on other apps as well).

https://www.loom.com/share/5bfea0ccb3514dfe9864fd59ed60383e

Important Details

• Version: Cloud
• OS: MacOSX Catalina
• Browser: Chrome

[areyabhishek]

@somangshu does the table search work as intended? Is Rishabh supposed to connect the table search field property to a search query?

[somangshu]

@areyabhishek we had this issue with the table widget when the client-side search would apply on the server-side search, This was resolved here and is in release right now.

Yes, the table widget search in case of the server-side pagination needs to be connected to a Query/API to get correct search results.
@Rishabhkaul could you provide more info on the reproducible steps.

[Rishabhkaul]

@somangshu I just forked the template from the Appsmith site (https://www.appsmith.com/templates) and continued using it (with the mock DB). And then I went and searched in the table.

[somangshu]

@Rishabhkaul @areyabhishek I have replicated this on the release environment and it seems to be working fine. However I can see some lag in the table widget in the Edit mode. Ill dig more into that. Let me know if you think the issue is resolved here.

If it is, then I would say we should update the template on the prod as the search query is not written properly and can lead to this or other errors.

[Nikhil-Nandagopal]

seems to be working on prod. @Rishabhkaul can you share the link to the app where it's not working and invite us to it?

[somangshu]

@Rishabhkaul After the release promotion yesterday this is working just fine. However the query written in the template is not correct and will result in wrong data population. Closing this.

[Rishabhkaul]

Ok that makes sense, thanks @somangshu! cc @vihar maybe have a look at the query at some point since its in the template.