Why native "Add" and form "Add" has a difference about related data?

  1. In adding item through top right + icon, you can create just totally a new form with no ability to relate any data as pre-filled data.

  2. But when you tried the other way by creating a form button (or just button with “open form” action) you are able to bring in columns which you made-related, to make it as a pre-filled data.

The question is why? Why can’t both of them act the same way? I think the preferable one supposed be the 2nd one when some data is available.


The open form button is usually a part of a details layout or a details screen and hence you have specific data from that screen which belongs to one row. Glide allows users to push that data in a form button.
In case of the add button, it’s always a part of list layout and from that screen you never have data from one specific row but rather you have the data of the whole sheet. How would Glide identify which row data you want to push through that?
I think that’s the reason they wouldn’t be able to implement this.


I thought I asked the same question.

I understand your logic but both refer to a leaf so the question remains open !!

1 Like

Manan is right. In an add icon scenario, it’s expected that users see a list of items from a specific screen and wants to add something with the same structure of data to that same list.

With a form button, users can add data to any sheets, which gives more flexibility and they don’t expect to see that data in the same screen, in my view. That gives us the ability to add in many columns from the prevous screen to the form.


Yes ThinhDinh it also makes sense.
But the list (unless I’m mistaken) refers to a sheet.
But I maintain my support to Everys for this new feature requests.
I had the problem, in “+” there is no Form button for example so impossible to make a complete form in case of linked sheet, so I had to do it in several steps.
Why not have the same possibilities in both cases

1 Like

Yeah the list refers to a sheet but not a row while the details screen of any sheet refers to a specific row. That way you can push column data from that specific row in a form button.
Which row should be chosen to do so in the add button? It’s difficult to define that because the add button comes from a screen which refers to a sheet and not a row.
I think this is the reason. The Glide team can add some special values in the add button too with dropdowns maybe to select the row to send data from.


Yes we all agree that, as it stands, the “+” button or the “show form” action adds a line to a sheet and does not refer to any particular line.
But if we don’t limit ourselves to what we see but what we can do, as the list refers to a source (in the tab property) it’s the same as a form button.
You can very well create a new tab in details format with a Form button to add a line to your sheet.
So why not ask for the modification of the “+” (however I am not stubborn, but pragmatic :grinning:)
But I think we’re not gonna be okay :wink:


I think the way we can predefine things using default values could lead us to some new possibilities. So I hoped this one would be considered by the Glide team, well, if there’s really a good reason to do. thanks!


The + button is from a list view. The list view doesn’t have any information stored which can be passed on.
The form button is from the details view, where information from a row can be passed.


So, it came from the different origins. Totally understood.

Now, in user’s eyes, I cannot always maintain the Adding experience with just one consistency way. Sometimes I have to omit the top-right + sign and create a button for adding just to follow the rules.

In terms of development, yes it is 100% systematic. In terms of usability, we made it hard for end users to keep up the same behaviours. If developers will not compromise about this it is also understandable. I just tried to point out a way Glide could maintain consistency in ux designer’s eyes.

1 Like