Any plan of support multiple rows? I have lots of apps need to use this feature. I add many new rows and submit them at one time. and database save time at one time, instead of add one row a time and save it to database per time.
Because this will consume a lot of time
Now my alternative solution is add a new avariable to keep the new add rows.
There are many to many and one to many in data relationship, adding this feature will help us a lot. thanks.
Has there been an update to the target release for hosted deployments yet?
Thanks in advance,
David
Hey @AnsonHwang -- so far we have no plans to support multiple rows. But we will be sure to update this thread if/when that happens!
Hey @DavidM -- the numbers I put in the original post should still be true! :
on-prem version 3.44-edge and 3.47-stable
I'm not seeing a 3.47 stable release here, and nothing in the notes for this feature in the 3.44 edge release related to this feature.
Am I looking in the wrong place?
Thanks,
David
Hey @DavidM, I will be tagging in for Darya! Apologies for the confusion on our part, but this feature has actually been released on 3.46-edge for self-hosted users ( just tested this on my end and can confirm).
Thanks @Blake_Reed
I presume we should have a new stable release coming in the next few days as 3.33 was in Feb.
Cheers,
David
Hey! @DavidM
You are correct! The next stable release (3.52) is scheduled to be released next Tuesday.
Hey, @Darya_Verzhbinsky,
thanks for adding the New Row Feature. One thing i noticed is the following:
I have an empty table and would like to give the user the opportunity to fill that table. However i am only able to add one Row. If i finish the new row i see that the changeset array gets a new element for a millisecond and afterwards its deleted again and the table is empty. So i am not able to add more then one Row.
The new row is correctly added to the newRows Array of the table state.
I had to create two actions on save, with queries reading from one of the two arrays
One with only run when:
{{self.changesetArray.length > 0 }}
and the other with:
{{self.newRows.length > 0 }}
You can use one save action with input from both arrays. Function concat.
David
A post was split to a new topic: Issue with Clearing table.newRows After Adding New Row in Retool v3.64.0-edge
Hello, thanks for the input @DavidM, @Davidkm! I tried the following two save actions but non of them are working:
table.data.concat(table.newRooms) & table.changesetArray.concat(table.newRooms)
I can see that nothing is happening to the data as well as changesetArray when executing the save action.
Hi @Darya_Verzhbinsky, thank's for this great new feature!
An issue I am currently facing is the generation of new rows key ID. Is there any running development to add them automatically?
(or Overall, ease the modification of keys in this context)
I am working with this feature and I like the editable on new row only a lot. But I have a use case where I want some of my data on the new row to be default when creating that new row like a foreign key to be my selected default value. I am a little lost how I would achieve this.
I am using a filtered table from a foreign key and creating new row is like adding a new note attached to that key. So I dont want to have to search for the key in a long list of possibilities every time I want to add a new record
I love this new feature btw but I'm having an issue where my column is conditionally editable (dependent on the account type). It works great if I'm editing. However, I would think that the same condition statement would apply for the new row (as per the guidance: * Users can only edit cells in the new row if their respective columns are editable as well.) It seems to be disabled. Right now, it seems to be that only the columns that are fully/always editable are enabled for new row. Is that true or a bug?
Hello, @Darya_Verzhbinsky , any update about multiple Rows.
Hi all, wanted to address some of the questions here!
Support for adding multiple rows at the same time is not explicitly on our roadmap at this time. It is something we are considering.
@Laurin_Boujon1 usually the key would be generated by your database. Is there something else you’re trying to do? If you want to generate it client side, I would suggest doing it in the query that you’re using the persist the new row.
@Derek unfortunately there is not currently a way to set default values
@Tiffany - unfortunately that is how it works today, only explicitly on/off works for new rows when setting the "Editable" property
I am looking for an add on to this feature. I have the user navigating to this table, typically the user is coming to the table to add a row. I don't see a way to Add a row without clicking the Add Row button. It would be slick if I could have the table default the Add Row state and the user could arrive at the table and just keep plugging values in.
