Anyone knows how to reset the input inside a cell?
I am creating a table with input fields that reads from an external API.
After the user changed the input field, I cannot reset the input to display the original values.
Things I tried:
“Reset a group” workflow of the parent group of the table. Nothing happened (contrasts to RG)
“Reset relevant input”. even there’s a button action relate to the input, it doesn’t reset.
Added a button to a row to reset the parent group of the input. It loads forever and raised an error.
Putting the table in a reusable element, then reset the whole element.
Clear the table’s data (via custom state) and loaded the data again. the input still retains the changed values.
Reproduction Steps:
Create a Table element under a Group ‘Group Holder’
Set its type to a User (Or any other data type). Set the data source to any list of the data type.
Create an Text Input in a cell in the repeating rows.
Set the initial content of ‘Text Input’ to 'current row’s user’s email. (or relevant data type’s text field)
Add a button that will trigger ‘Reset group Group Holder’
Preview the page.
Make some changes to the email text input.
Press the reset button.
The input field stays modified.
You can repeat the exact same thing with RG but the input in a RG row will reset.
Updates:
I found the major culprit to be “reset a group” of the parent group of the table.
After I reset the parent group, buttons within a row seems to bug out.
If I don’t reset the parent group, “reset relevant input” works out as fine.
Great update! Having the Table’s List of Xs as a data source in another element is a big step forward. Are we also going to get the ability to “display list in a table” as we can with repeating groups? That’s an essential feature for setting up daisy chain filters (which are very important in dashboards). Sorting and filtering tabular data is what makes the table element most useful, IMHO. Thanks!
Now that the table’s List of Things is accessible, you can just create a workflow with the Download CSV action and reference the list of things. Put a Download CSV button above the table to trigger it.
How is the Table element working for everyone at this point? I held off on implementing it into my apps while they worked out the kinks and added some more features.
I want to swap out many custom tables I’ve built for the Table element. Does anyone care to chime in on your experiences with it?
(Bonus points if you talk about your experience with it on mobile!)
Hi everyone,
I’m having issues with the new element “Table”.
Before upgrading to Bubble version 29, I had severe issues with autobinding and deleting items. If I edited an input value autobinded to a row’s item field, 99% of the times it didn’t get modified. All privacy rules were set up correctly.
Similarly, if I started a workflow by clicking on a button in a table, to delete that row’s item, the loading bar appeared and started loading for 30 seconds. After that, the item was not deleted at all.
Now I upgraded to version 29, and those 2 issues seemed to be gone, but another one arised: after hiding and showing a table, all the items in the row are not rendering anymore:
I’m trying to isolate the bug in a demo page before submitting it. Also, I’d like to check if anyone else is having the same issue, and maybe can help me faster.
Thank you @ihsanzainal84 for your suggestion, that was my first guess.
Unfortunately it’s not that and I think that I’ve stumbled onto a weird bug:
The red background that you see in the first column is triggered by a condition that says: “when this input value is empty, change the background to red”. The element is an input binded to one of that row’s element fields.
What’s stranger, is that the table has elements in it - you see it inspecting the table and counting the rows, which number is exactly the number of things in the table. BUT, the row element is empty.
I have found that the only good use of the table element for my apps is in building static tables. I use an option set, with an option for each row and field for each column (e.g below, Issue is an attribute and Action Required is an attribute).
Then just display the option set in the table source, add a header and text. I found it much quicker than setting up an RG.
The last update was from @kate.mcnally just under 4 months ago which said they have exposed two new states. I have built many plugins before and if I was tasked with this, I would be quoting about 10 min of work. Given that native elements are likely more complex than bubble plugins, let’s give them the benefit of the doubt and say it’s 20 min of work. The updates to this HIGHLY requested feature are basically non existent despite all the bugs and lack of features that people have posted about multiple times in this forum thread.
This element is a joke IMHO and doesn’t even come close to replacing the functionality of a header row group with an RG underneath.
The lack of attention to new features built out by bubble is really starting to piss me off. I am a full time developer and if I delivered unusable features like this to my clients, I would very quickly not have any.
