I have a question about the “items until#” operator. I use it to display tasks in a repeating group. It is based on a CS and the default value is 3. The number of lines in the repeating group is not fixed because users can click a button to display the rest of the list.
The problem is that even though only the first 3 tasks are displayed in the repeating group, all tasks are loaded by default in the console, and I don’t understand why…
Is it the normal behavior of this operator or am I missing something?
This is expected behavior in Bubble. The :items until # operator limits how many things are shown in the repeating group, but it does not change how the search is executed behind the scenes.
When the page loads, Bubble still performs the full “Search for Tasks…” query on the server, gets the whole list back, and then applies :items until # on the resulting list to only display the first 3 in the RG. That’s why you see all tasks in the network/console, even if the RG only shows 3 rows.
If you want to really limit what is loaded from the database (for performance reasons), you need to:
Use constraints in the search itself, or
Use the “items from # … items until #” pattern with the “Allow load more” / pagination-type setups, or
Move to a backend workflow / API pagination where you control the cursor / limit.
So you’re not missing anything in your setup – :items until # only slices the list on the client/UI side, it doesn’t act as a database-level limit.
Unfortunately no, you don’t - as the above explanation is completely wrong (probably more AI rubbish).
:Items until # should, and does, mean that only items up until the specific item will be fetched from the DB.
What’s going on here is likely either to do with your main (non-conditional datasource), or the same data being used elsewhere on the page (with no limit).
But there’s no a lot of information to go on…
So feel free to share more details if you want to find out what’s really going on here…
I have tried several things and it’s now solutioned.
To bypass this issue, I operated as follow:
One RG named “VAR Taches” with the until operator (based on the CS) and limited rows set to 3
Another RG where the data is actually displayed with “VAR Taches” as datasource and without limited rows
Because I still don’t know why but when I was doing the same thing within a single repeating group and without limited rows, all results were displayed in the console.
