I’ve got a base that has one single choice column with a default value.
This value is correctly added when I create manually a row in the base
However, it’s not the case if a line is created by a webform.
I have to put the field with its default value assigned and to disallow its modification, to be sure it appears well in the table.
I reproduced that in a fresh new base.
For a date, i can get it, but for the default value of a column, like a status, i really don’t get why this choice was made.
So counter intuitive for me.
Could you think of adding a trigger in the webform that fills default values ??
With the exception of the collaborator column, it’s the same column types for which you can define default values in the base editor.
Having different default values in the base editor and the form editor may be counter-intuitive (for you), but it gives you a lot of flexibility when creating your use cases.
I don’t get why two column types should be treated differently. Wouldn’t that cause maximum confusion?
Might I suggest it would be a good idea to allow for invisible fields in the webform builder? That way Ben can assign the default “new” in the webform but it would not be displayed in the frontend form. I know many form builders that allow this functionality. What do you think @Ben ? Should that be also added to the ideas forum?
@webdienste Indeed, that would be a perfect solution.
Still I think its counter intuitive to have a webform filling a table without default values that are supposed to be added by default to every line