Interface Forms New Features Today

Question

Great session today! I really enjoyed it! I wanted to follow-up to clarify my question and see if others have ran into the same situation and if anyone knew the solution!

So, I have an interface form with the new form builder. Within that form, I have separate groups based on what a user selects initially -

1 - User puts in base info

2 - User selects the option

3 - This group displays when a specific option is selected in 2 (So it's conditional)

My question is.. when I added a field in the group 3) (In this example "Hit Time"), I can't seem to be able to "re-add" it to another group. So say that user selects a different option for 2), but I use that one field "Hit Time" for multiple options in 2. When it is in the group, I can't use it in another group.

Is there a way to do that? Or is the current solution to only group specific fields that are not required for different conditional options. Thanks all in advance for the help!

Best answer by Russell_Bishop1

So I think you're absoluttely right in terms of what is possible – all of Airtable's new 'single record' interfaces (forms and record details) treat fields as a show/hide/group, as opposed to being an instance of a field.

If I were re-designing your form, I would separate any field that appears for 'two or more conditions' (e.g. if A or B or C) and have it display separately from your conditional groups.

Definitely less slick though (and harder to manage for you).

Russell_Bishop1 · Accepted Answer

So I think you're absoluttely right in terms of what is possible – all of Airtable's new 'single record' interfaces (forms and record details) treat fields as a show/hide/group, as opposed to being an instance of a field.

If I were re-designing your form, I would separate any field that appears for 'two or more conditions' (e.g. if A or B or C) and have it display separately from your conditional groups.

Definitely less slick though (and harder to manage for you).

jordanoverton · Answer

Yeah, this is exactly the route I am planning to take, at least for now. The current version of our form is fine (it uses the old way of creating via form view on a base), but the features presented (validating an email, etc.) are something we'd like to take advantage of in the future to cut down on errors.

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded