Hello everyone, i came from Bubble and some terms are diferent here in wappler…
In bubble i was using repeating groups (in wappler, repeating children) and i used to sent the repeating group info to another page. I used to have like a dynamic page that received the info from a specific data and the page displayed more information about that repeating group.
Let’s say that i have a database called “notes” and i have quite a few notes, then the user should see all his notes (trough a repeating children) and choose one. When he clicks on the choosen one the page should sent all the information from the repeating children to another page that was built only to receive that information .
Hi Rodrigo. You can use Wappler in the way you described, sending the user to another page to display additional information about a selection made, but Wappler has a better solution that uses a single page. The server-side component called a "data detail". It will load the data from your query to the client, but you can set filters to show only subsets of that data initially. When a user clicks on a row or makes a selection, or types in a search, you use the data detail to show the additional (hidden) data for that row/selection/search.
If you wanted to use Wappler in the way you described, then you would use query parameters (URL parameters) to pass the selection to the next page, which would then display all the information.