Suggestions - one better dynamic filtering

🤝 Discussion
1

Hi everyone! :wave:

I’m currently working on a table that needs both pagination and filtering on most columns, but my current setup has turned into a bit of a mess — too many components, and it's error-prone.

I’m wondering if there’s a better or more efficient way to handle this. Specifically:

  • What are the best practices for implementing server-side pagination and filtering?
  • Are there any recommended components that make this easier and more reliable?
  • How do you manage filters cleanly, especially with multiple columns to filter?

Would love to hear your suggestions or see how others have approached this. Thanks in advance!

2

currently this is how my filters looks, too many components. is there any better ways to apply dynamic filter with pagination? that dont involve that many columns? and i can add more filters on more column if i want easily?

image
image1468×202 4.75 KB

3

BUMP , Any ideas?

4

BUMP — Maybe my question wasn't clear. Let me rephrase it:

I'm looking for ideas on how to apply dynamic filters using SQL, especially since I'm implementing pagination on data tables.

The issue is that filtering across multiple columns requires me to add a lot of text inputs and dropdown components, which gets cumbersome and messy.

Is there a more efficient way to handle this — ideally a solution that allows filtering on many columns without needing a separate component for each filter?

5

Hey @Jagdish_Parmar - thanks for reaching out. I assume you're referring to server side pagination? There's a native filter component that would perfectly suit your need, otherwise.

image
image1112×618 39.7 KB

This same component could theoretically still be used to build filters for server-side pagination, but interpolating the contents of filterName.value.filters into a SQL query would be challenging.

6

thanks @Darren yes, i was refering to server side pagination, the filter button is a good option but it filters only the data present on page

7

That's what I figured, but thanks for confirming. :+1: It would technically still be possible to use the filter component simply for its UI, leaving it disconnected from the table and interpolating the contents of filter.value.filters into your SQL query, but that would be a super manual process and probably error prone.

How flexible do you want these filters to be? Are you satisfied with just defining a column and value and filtering for equality? Or do you want other comparison operators?