Hi,
I have a table in Xano that holds over 250k records and I trying to create a collection.
I tried using the new iteration of tables using Xano integration but that tries to make a mirror image of the entire table and times out.
I then tried the old method of a plugin but when I define the collection again the Fetch Data step fails as it tried to pull all the data even though I turned off Fetch Automatically.
How should I proceed?
Thanks
Steve
I don’t think you want to have a collection filled with 250k records. You will want to paginate it using the options in the Xano Query all records action before sending it to WeWeb.
Ok,
If I paginate in order to get the view created how does this affect subsequent searches? Does the search look through the initial 200 records rather than the full Xano table?
Steve
Depends on how you setup the search. If you use the search term as a query parameter in Xano, it will search the entire table. If you bind the search term to the WeWeb filter option in the collection, then it would only search the smaller paginated set of records (generally you wouldn’t do this).
This is a helpful video on how to setup Xano pagination with WeWeb:
Hi Joyce,
I had watched this before but if you look back at my initial query, the problem is that my Xano table has over 250k records. If I do not use pagination, I get network errors between WeWeb and Xano. A suggestion was made that I should paginate in Xano which I have done - 200 records, so I can create the table and the view successfully.
But they only contain 200 records. If I run a search against the table for a particular field (product name = “Chicken Tenders”) and the data that I am looking for is not in those 200 records how do I or (how does WeWeb) go about searching the rest of the Xano table?
Steve
Steve, as I said, you need to perform the search in Xano, not WeWeb. You set an input variable (eg searchTerm) on your endpoint. Then use that input variable in the custom query parameters of the Query All Records. Make sure you check the box for “Ignore Empty Values” so when the search term is empty, it ignores the filter. See this example for searching Client Accounts using a search term input to match against the account name and billing street.
The order of operations in Xano is 1)perform query, 2) paginate (if setup). So it doesn’t matter what records were previously returned to WeWeb, if you update the search term in WeWeb and trigger a new collection fetch (calls the Xano endpoint), it will use the new search term against all records in your table.
You should be able to play with this on a smaller table of data, or just stick a temporary query parameter (eg. record ID < 1000) on the Query All Record that reduces the record count while you work on setting up the search and paginating configuration.
Hi Eric,
Thanks. I made that change on the Xano side and can now pull data into the datagrid but for some reason when using the traditional collection, the data shows and then disappears only showing 1 result.
And if I use the the new Data and Views, the TABLE VIEW results are empty (I am using another table for this example) but the same thing happens with the one above.
Thanks for any assistance.
Steve
Well, unfortunately this is where WeWeb has royally screwed up how they’ve designed the latest iteration of WeWeb and will lead to this kind of confusion. Not sure why there is this new abstraction layer when using an external database, but here we are.
I only use the Interface tab of WeWeb and the use the original Xano plugin to connect to my Xano instance. Can’t help you with how things work in the Data & API tab of WeWeb and these new table views. I only use collections and bind the collection directly to my tables and datagrids.
Thanks.
As far as I can gather the plugins will be deprecated at some point in time and I do not want to build out an app only to have to rebuild it, but it is a bit frustrating working with Table Views as there is very little documentation and no video demonstrations.
Always wonder why companies tend to leave documentation to be the last thing to be done.
May be @Joyce or @ishika can let some guidance.
Steve
