When grouping records, another column is added to the UI. In tables with a lot of fields, this takes up valuable horizontal real estate. It would also be nice to have the option to collapse each group.
I don’t want to say you should blatantly rip off a competitor, but I really like how Airtable handles this. Borrowing some of this UI would greatly improve the experience when grouping records.
Thanks for sharing this great idea, @shawn! I’ll communicate it to the team. 
Hey @shawn, I’m back with some updates on your feedback. We plan to implement all the features you mentioned. Here are the links to track the progress:
Hopefully this feature will be implemented soon 
Not sure why there wasn’t such a feature already, since it’s such a crucial QOL feature when groups are used.
And conditional rollups/lookups too, which are even more important, imo — I’m rebuilding the database from Airtable, but even after Airtable import feature, it’s such a massive PITA, because the Airtable one used conditionals quite a lot.
For example, lookup the “Price” in “Invoices”, but filter only ones with “Unpaid” (or “Paid”) status in “Status”. I’ve created so many fields to create workarounds and, not gonna lie, I got pissed off so much while doing this.
Honestly speaking, I thought transition from Airtable to Baserow would be so much easier. I understand that Airtable is a super-duper-massive company, but lack of some features is mind-boggling. There are “Automations” and “Applications Builder”, and even an AI “companion” while core functionality (Databases) need lots of UX tweaks (I listed only two, but I have more issues that I will give feedback on later). I might be wrong, but I don’t think Baserow has such a massive team with different dev groups that are focused on multiple things, hence why I don’t understand lack of UX in quite many areas.
P.S: Not trying to offend Baserow team, I’m not saying Baserow is a bad product, I do think it’s pretty nice and good, but I thought the number 1 alternative to Airtable would be very toe-to-toe with it, but that’s not the case. I’m half glad that I offered Baserow as an alternative to my client, half upset and think that I should’ve kept using Airtable instead.
Hey @Georgy, thanks for the detailed feedback!
We’re actively working on improving many UI/UX aspects of the core database and addressing smaller issues as quickly as we can.
For example, collapsing rows in a group by is currently planned for Q2:
Conditional filters for the Lookup field are also on our roadmap:
I have a question that has been bothering me for roughly the same amount of time it takes a child to enter primary school.
I have been following Baserow grouped views for a long time. The original grouping request goes back years, and the dedicated issue for collapsing rows in a group by appears to have been open since December 2023. The latest public context I can find suggests this is planned or in progress, but I cannot tell what the realistic delivery path is.
What makes this confusing is that the current Baserow documentation describes grouped rows as collapsible sections and also describes multiple group levels / nested groups. In practice, at least in the views I am using, grouped rows still behave much more like a fully expanded grouped table than an Airtable-style drill-down interface.
So I have two concrete questions:
This matters a lot for real business databases. Companies OS, CRM systems, accounting databases, VAT trackers, project management tools, inventory systems, and many other operational apps become dramatically easier to navigate when users can collapse top-level groups and drill down only into the section they need.
For example, a VAT or accounting table grouped by Company → Month → Status can become unreadable very quickly if every group is permanently expanded. With collapsible groups, the same table becomes something a person can scan, audit, and operate without endless scrolling.
If the blocker is development capacity, I would genuinely be willing to contribute code or sponsor development. If there is a technical blocker, I would be very interested to understand it. If this is already on the roadmap, an estimated version or timeframe would be extremely helpful.
And while I am here: thank you to Bram and the team for finally bringing 2FA. Civilization advances one step at a time.
I remain a loyal Baserow user, though increasingly amused that after more than 1,000 days I can still collapse a cardboard box faster than I can collapse a group in Baserow.
Hey @rs369, group by improvements are currently in development and we plan to release the updates at the end of June. Soon you’ll be able to:
→ collapse groups
→ apply summaries per group for totals, averages, counts, and more
Take a look:
Thank you for the update you shared a couple of weeks ago. I was really excited to see that grouped view improvements were finally on the way.
Since we’re now at the end of June, I was wondering if there’s an updated timeline for the release?
I was looking forward to the native implementation so much that, in the meantime, I actually ended up building my own custom grouping system (see the attached screenshot). It works surprisingly well, but I’d much rather use the official Baserow implementation once it’s available.
I’m especially looking forward to:
These features would make a huge difference for larger operational databases like CRMs, accounting systems, VAT trackers, inventory management, and project management, where permanently expanded groups quickly become difficult to navigate.
Could you share where development currently stands? Has the release been pushed back, and if so, do you have a realistic ETA? Even if it’s “a few more weeks” or “next month,” having an updated expectation would be really helpful.
Thanks again to you and the whole team for all the work you’re doing. I’m genuinely looking forward to replacing my homemade solution with the official one as soon as it’s ready. 
Hey @rs369, great work with group by 
Our goal is to release the Group by improvements next week.
The release is currently planned for next week (July 8–9). Please keep in mind that the date may still change, as some features are currently under review. 
Apologies for a silly question, but I assume “Group by improvements” and “Button field” are exactly those things we discussed here and, as for the latter, it is a fix for a button not being greyed out, correct? Or is it a new improved field that can execute actions, like Baserow Automations? That will be super awesome.
Can you also please tell what are Additional integrations in Automation?
And since I’m asking a bunch of questions here: can we connect our own AI (Ollama, Gemini API, etc) for use with Kuma or Kuma is a dedicated service only?
Hey @Georgy,
The Group by improvements will include:
As for the Button field (please keep in mind that it’s not in development yet, so it won’t be part of the upcoming release), it’s a new field type that will let you trigger certain actions directly from the database, yes.
Can you also please tell what are Additional integrations in Automation?
I’ll check with the team to see if we already have a short list.
And since I’m asking a bunch of questions here: can we connect our own AI (Ollama, Gemini API, etc.) for use with Kuma or is Kuma a dedicated service only?
Yes, if you’re self-hosting. You can connect your own AI provider:
Fire! Thanks a lot for the heads-up!
