Yes, for sure. You could add a filter on your collection when you setup your collection or on the page when you bind the collection to your collection list.
It explains how we organized our data, fetched our list of lessons and courses in WeWeb, and filtered our list of lessons based on the course selected by the user.
In this case we’re using Airtable but the same logic would apply to Xano
The videos have been very helpful! And the filtering capabilities of WeWeb are great and intuitive. I’ll rewatch the videos in case I missed the answer to my question. But I think the difference is that I want to Group dynamically. So I wouldn’t want to set up a few collection lists filtered by category. Rather, I am looking to have one collection list that can be grouped based on a dynamic value from the database.
I am setting up a multi tenant app, so some users might belong to an institution with 5 class categories, whereas another user’s institution might have 10 class categories, for example. So, I would need the grouping to be part of the repeating group.
You would like to filter the data in the backend based on the user who is logged in your WeWeb app so that WeWeb only fetches the relevant information from Xano. Is that correct?
Not sure if this is possible in WeWeb, but you could try nested collection lists. The parent list would be a list of categories, and the nested list would be classes for that particular category.
This sounds awesome! How would you go about doing this? In Bubble, there is the option to select “current cell’s _______” and I am trying to find the WeWeb equivalent. Would you do this through filters? What is the most efficient and best practice to fetch nested data?
-An example of this use case would be a repeating group aka collection list of Feed Posts with a nested collection list of comments and another nested list within that of comment replies.
@Joyce Hi Joyce! I have a separate comment table and a separate post table and each comment has a related post and there is an optional section that can be blank for related comment, meaning, if a related comment is filled by a comment’s unique ID, that means it is a comment reply.
Most applicable scenarios in my app have a primary table that I would refer to almost as a data parent, and anything that would be a “child” of that parent (i.e. a comment would not exist without a post) is its own table with a RELATED field that references the parent.
create one posts collection in WeWeb, and use Xano add-ons to send the posts + linked comments to WeWeb.
create two collections in WeWeb (one for posts and one for comments), and use the lookup formula to display the comments data in a posts collection list. Here’s a video on how to use the lookup formula in that context.
Hi Joyce! Thank you for all your help on this. I wanted to inquire whether my Xano collection list that is being referenced in the lookup formula must be public or whether it would be private and have the lookup function still work?