Since people seem concerned about the lack of updates to the Table element, I’ve put together a list of ideas about the Table element currently on the Bubble ideaboard - the official tool Bubble use to track user suggestions. You can find it in this post. I’d recommend upvoting what you’d find helpful and adding ideas you think are missing to the Ideaboard.
3 Likes
Has anyone hacked a way to get sticky columns?
I wish this was offered! Seems like a miss, since we have the sticky row.
yes , i did by creating 2 table and grouping them in a row group, the first one has only one columns and the second one has all the other columns
2 Likes
Thanks @gerbertdelangen! It’s a bit circuitous but works.
1 Like
Any idea on how to activate the horizontal scrolling ?
1 Like
Wrap your table element in a group and make it 100% width and add to that group a class (classify plugin). You can then add this css to force the scrolling.
{addClass: “my-class”}
```.my-class {
overflow-x: auto !important;
}```
Hello,
I have a problem to access to custom state of a reusable element inside the table. I want to know how to get access (page) to the customs states of my RE dropdrown ?
You should probably start a new thread for this type of question.
Regardless, check out the Antenna/Satellite plugin:
Thank you very much for the recommendation! I try to avoid using plugins as much as possible, but if it’s really the only viable solution, I might consider it.
That being said, I’m wondering if this limitation is due to the fact that the Table Element is still in beta and that access to custom states of Reusable Elements hasn’t been implemented yet (Team Bubble)?
In that case, is there a workaround that others who have faced this issue have used without relying on a plugin? Otherwise, if a plugin remains the best solution, I’ll give Antenna/Satellite a try to see how it fits into my workflow.
Thanks again for your help!
The challenge you cite is unrelated to the beta status of the table element. For a page-level action or element to reference a custom state of a reusable element that’s replicated for every item within either a table or a repeating group, there needs to be a mechanism for the page-level reference to reconcile which of the multiple reusable elements is intended. There’s no native way to accomplish that. Plugins like the one I cited fill that gap in Bubble functionality.
I finnaly use Toolbox by running JS to make it work. Thanks again for your help!
The Table element always seemed to me like the missing ingredient to improve desktop applications. Although RGs are flexible, they require development that could be part of a table, such as sorting, filtering, etc. However, more than a year later, it doesn’t seem like this element will improve or leave beta. Basic functions like paging and refreshing are still missing.
I admire Bubble’s focus on developing and following trends, but I think they’re also forgetting the basics that made this platform great in the first place.
7 Likes
I’ve lamented the lack of development on the table element for a while. Yea, they dropped the ball on this one.
I’m also quite surprised that Bubble’s Table element has been stuck in beta for over two years now. It still lacks essential features like pagination, sorting, and real-time refresh — things you’d expect to be native by now. More broadly, it seems Bubble tends to underinvest in native elements and prefers to rely on third-party plugin developers to fill those gaps.
1 Like
Hi everyone - just hopping in to say we will soon be taking the Table Element out of beta, with the planned release of the following features:
-
Pagination workflows & conditionals
-
Other missing list wf actions like “display list”
-
Ability to add footer rows
-
Ability to set alternating row colors with “This row’s index”
Based on user feedback and common table use cases, these are the highest priority features. If you believe we’re missing any other key features, please let us know in the thread. Thanks in advance!
19 Likes
this has made my day 
Thanks @nick.carroll
3 Likes
Excited to hear the table is finally getting some love. Once it’s out of Beta hopefully there will be occasional on-going upgrades since it can be such a key part of everyone’s apps
2 Likes
Hi Nick, this is great! There is a very anoying problem that if a column is hidden, the width of that column still computes for the overall table width, leaving a massive gap on the right hand side that you are able to scroll to. If that could also be addressed, it would be great!
Also, row or column reordering by drag and drop, would also be really appreciated.
2 Likes
Also experienced this, and it actually made the whole table even wider in my case
@nick.carroll can we get Columns in the Elements Tree or accessible through the main Table element?
If it weren’t for @gerbertdelangen sharing this tip I don’t think I would have ever been able to find how to access the ‘not visible on page load’ Columns as they don’t show on the Editor page unless selected
1 Like