you could load all the data inside another repeating group, then point this repesating group that you are scrolling to that repeating group. hat should work. The reason RG behave that way is because bubble tries not to load more than is needed from the database per time, but if you “force everything” to load in repeating group A, that should work. You can also put conditional in RG B(the one you would be scrolling) to only show when the 2000th item(or a high range than corresponds to your situation)in repeating group A isnt empty…that way you are sure RG A has all the data it needs from the database!
I had not seen that. It is pushing the page to work as I hoped. There is a huge delay now though, I am getting browser warnings asking if I want to wait for the page to load. There is nothing much on this page but a dump of API data. Surprised, I didn’t think a page would have this much trouble displaying text values from the API call. I may have to alter how I am displaying the records. Wondering if multiple repeating groups would help.
The only reason I think so is that the API data comes in a linear dump and I have to filter by two fields (year and position in the list) to display each item. Default display is 5 years / 5 columns of data, so there is a lot of logic that is firing to build what appears to be a table of information from that linear data set. I may ask the API developers to adjust the output as well, so that I don’t have to calculate so much. The other option is that each column represents a year, and I can call the API and limit it to 1 year, then call it 5 times and then output each result set in column… probably less work for the browser to do it that way. Oh this one is going to be fun : )
