Currently when pagination is activated on sfPegListCmp, filtering the records work on the data already retrieved with respect to the paginated data already retrieved from server side.
Example below:
Total number of records as per query: 444
Number of records displayed per page: 50
Page number: 2
Filter type: All or single value
Filter result: 22 records from the 100 records only (pagination) are displayed and not from the whole 444 records.
Conclusion:
Only records fetched with respect to pagination are filtered.
Filtering is done on client side on all the records (paginated) fetched initially from server side.
Filtering is not done on serverside; that is from the query itself.
Two evolutions are proposed (Either/Or):
Is it possible to carry-out the filter from the server side so that the search on records will filter from the whole 444 records instead on the 100 records fetched to the client side logic?
Is it possible to dispatch an event (Lightning Message Service/Platform Event) from the sfPeglist that will hold the count of records filtered from the whole 444 records instead on the 100 records. The idea here is to capture the event in a custom LWC in order to display the record count.
Hello @pegros,
Currently when pagination is activated on sfPegListCmp, filtering the records work on the data already retrieved with respect to the paginated data already retrieved from server side.
Example below:![image](https://github.com/pegros/PEG_LIST/assets/53938812/ff9d39fb-2faf-4dca-b524-b226af99749c)
Total number of records as per query: 444 Number of records displayed per page: 50 Page number: 2 Filter type: All or single value Filter result: 22 records from the 100 records only (pagination) are displayed and not from the whole 444 records. Conclusion:
Two evolutions are proposed (Either/Or):