I’m using the ‘Add Row’ action in Glide, but I’m only filling in the first field while leaving the rest empty. However, instead of adding a new row with just that data, it duplicates the last row’s information for all the empty fields.
How can I add a row while ensuring only the specified fields are populated, without carrying over data from the previous row?
Even when I enter a value (for example, writing ‘test’ in the ‘Descripción de su servicio’ field), Glide ignores it and instead fills the field with data from the last row.
In other words, glide is auto-filling empty fields with data from the last row instead of respecting the specific values input.
Are you using a form? (I can’t tell from your screenshots).
If you are, get rid of the Add Row action. You don’t need it. A form adds a row when you submit. That is its purpose.
I’m not using a form; instead, I created a button to duplicate a row. Let me explain the logic: in my business, a client can have multiple profiles. For example, my client Mateo might have three profiles, where most of the information remains the same except for a few details like price and address.
That is why i use a button, to duplicate the profile to retain all the shared information while leaving those few fields (price, address, etc.) empty so I can manually update them. However, when I try this, it doesn’t seem to work as expected.
If I used a form instead, I’d have to manually enter all the data again, which would take too long. Is there a way to duplicate a row while ensuring certain fields remain empty for customization?
I think I would start with building separate workflows. One to duplicate the row (applies to the row to be duplicated). A second to clear the values in certain columns (applies to the new duplicated row). It would feel cleaner and safer that way.
That seems like a weird solution though. The Add Row action should only fill columns you tell it to fill, instead of doing what it wants. Clearing fields after the fact seems like a workaround to a major bug that should be fixed.
Unless I’m missing something that I’m not seeing in the screenshots…
I’d have to play around to see if I can duplicate, but if the Add Row action is acting that way, that’s pretty scary.
Exactly, @Jeff_Hager, that’s exactly what I observed.
Here’s how the bug works:
When using the “Add Row” action, it checks the data in the first field.
If the first field contains custom input, it disregards any mapped predefined data for other fields, erasing everything and keeping only the custom inputs (if you put custom imputs in other fields, it will keep them as well).
On the other hand, if the first field contains predefined data (which is always from the last row), it doesn’t matter if you manually delete or modify the other fields—it will still pull all the data from the last row.
This behavior can be quite problematic and far from optimal.
