Client-side vs Server-side column filtering in a table

Question

I have a data table with approximately 10 columns. The rows load in a paginated / lazy loading manner, hence, around 15 records are loaded at a time until you paginate or scroll down. Now, I would want to apply column filters on this table using a list of multi select options. Should this list of options in the filter multi-select list contain only values that have already been loaded in the UI or all possible values that the field could have?

For example (using the screenshot as reference), I want to apply filter on the "Team" column. The UI has only loaded data for Team 1 and Team 2, however, there are more values that haven't been loaded yet (Team 3, Team 4, Team 5 etc). So the question is :

1. Should we only show Team 1 and Team 2 as options in the filter multi-select? This will be filtering values only that have been loaded in the UI.

   OR

2. Should we list all values that the column can have (Team 1, Team 2, Team 3 etc.) and make a server call to fetch records based on the selection?

Answer 1

If your intent is to have the user filter only the results loaded so far, then I'd expect you would only show terms relevant to those items.

I would expect, however, that if your user wants to filter the table to display only a certain category of result, the results they want to see may well include items that have not been loaded into the UI. Thus I would expect the filter options to be comprehensive across all of the records, not just those currently loaded into the front end.

STANDARD CAVEAT: I don't have nearly enough context of your system or users to say anything definitive, of course, so your best bet would be to run that by your users.