The current expression is do a search for:group by field A:count.
It makes many calls to display the count. The table is big. I wanna avoid having another computed table, if there’s a way to avoid that.
Thanks
Hmmm, a grouping should generally return all at once.
Can you share a screenshot of your search expression, your group by expression, and where it’s used?
1 Like
Any chance this is in an RG?
@georgecollier @Zeroic It’s a state
Instead of setting a state, try putting the same expression in a group data variable (hidden repeating group). Then Bubble will only load what it actually needs (it might not need the paginated group by results)
@georgecollier idk, I even tried the most default way(with fixed rows and without) in an empty page. It’s the same result.
Are you still looking for a solution? If so, please let me know — I’d be glad to assist you and help you get it resolved.
Is cost code a related data type? Is approximate count a field name on your data type? I’ve never seen approximate count as an operator before but I suppose new things can be added to group by operators.