Hi there. I’m following this tutorial https://youtu.be/hJDpWGyeQoQ?si=XR70Np_WQU5b7Tee and it works fine but only with No paginated Xano DB; when I try to apply it to a Xano Paginated database the search filter does not work in the backend & frontend.
I appreciate your assistance.
Hi @nico 
Can you provide a bit more detail about how things are setup on your side? Maybe share some screenshots or a short video explaining what you’re trying to achieve, how things are setup in Xano and WeWeb, what you tried so far, and where you’re stuck.
It’ll make it easier for us to reproduce your use case and help out.
Thanks!
Thank you for your answer Joyce.
I share with you my Xano & WeWeb screens and two videos.
When I use a filter/search in the backend it works correctly but there are a lot of records in the database so I made another api endpoint with pagination, it works correctly but when I add a filter/search in the backend it doesn’t work.
Xano debug video: Watch xanoSearch | Streamable
WeWeb screens
WeWeb video: Watch priority Search | Streamable
Xano support couldn’t give me a solution to Search in a Paginated Endpoint.
All their examples works only when Endpoint isn’t paginated.
Hi @nico,
when you use page and per_page in Xano, don’t use offset in Xano. it is either page and per_page (limit) or per_page and offset.
Use search only in the XANO query like tracking_number includes. Beware includes only works on string values.
In this way you should be able to use backend filtering, pagination and (external) sorting.
Sidenote: Sorting doesn’t correctly work on add-ons in xano. When it is implement it is only working on the current page. This is because in Xano add-ons are rendered/included in the response after the initial output of a query. In that case you need to use evals.
Hello @FHEXL
Query Search doesn’t work when API endpoint is paginated so i decided to paginate in frontend although my web app will run slowly. Thank you!
Hi @nico
What do you mean by “query search”?
I don’t know if it would solve your problem but, in level 2 of the Academy, we have a collection that is paginated in Xano and has a search input in Xano as well.
It seems to be working ok.
Here when I look for tickets that contain “unable”, Xano returns only one ticket:
And so there’s only one page in the collection metadata:
But if I don’t search for anything, I get the first 25 items from the table and information that there are 995 items in total so 40 pages overall:
Does that help or not at all? If you want to take a look at a starting point, don’t hesitate to take a look at our ticketing app template and the Xano snippet that comes with the academy course:
