Hi all,
I’m struggling a bit to apply paging to a repeat region. Any help will be appreciated.
I followed this guide (https://docs.wappler.io/t/nested-repeat-regions) and followed the steps to the point. As per this guide, on the server side, query1 fetches parent records and query2 (within a repeat loop) fetches child records.
On the front-end, data binding is on “repeat1” data through serverconnect1 as per the following pic
Now, as per the other guide https://docs.wappler.io/t/applying-dynamic-paging, paging can be achieved by using a paged query, so I converted above “query1” (parent record) into a paged query and got the offset variable set as well.
Now, as you can see in the above screenshot, the parent-child combination is on repeat1, so when I bind with repeat1 query on the front-end, i lose the ability to query the next pages by adding the bootstrap pagination component (connecting it to repeat1 - the same data source). See below picture from the guide https://docs.wappler.io/t/applying-dynamic-paging where the bootstrap pagination component is connected to a query that has paging capability.
Has anyone tried achieving this? Esp - laying out nested-table along with sorting, paging on parent level & filtering across both parent & child records. @UKRiggers - I see you have been doing something similar - https://community.wappler.io/t/how-do-i-search-on-nested-repeat-regions
I’m a newbie, so still learning to figure it out, any help will be greatly appreciated. Many thanks!
Last updated: