Two of my biggsest gripes Airtable are: 1) not being able to add records when the view is grouped, and 2) having records disappear as they are entered if the filter field is not set.
Instead, what if Airtable always defaulted the fields in a new record to match the grouping values where it is created? For example, if my view is grouped by Project and Task and I add an item in the Project “A”/Task “B” subgroup, how wonderful it would be if I could add a record there and have it default to Project A and Task B!
Setting defaults this way would also go a long way to making life easier for those of us who use a lot of filtered views. If the groups also covered the filtered fields, I wouldn’t have so many new records accidentally disappear because they no longer match the criteria.
This field default idea sort-of works now in the Kanban view. When you add an item to a list, the value of the single select that the view is based on is set to the value of the list. I say “sort of” because it’s too easy to enter an item into a list and watch it be filtered out of the view.
Also, I wish that there could be a “require filter fields” option that simply would not allow users to enter data into filtered views without setting the fields on which the filter criteria are based and smartly offer default values to match the view being worked on.
... View more