As @AlliAlosa mentions, Airtable does not currently support conditional logic; however, depending on your use case, there likely are ways of achieving what you need.
|
|
|
|
One caveat, though, is that much depends on what you mean by the term ‘form.’ Airtable uses ‘form’ to mean a specific view used to add records to a table. As a result, there are special capabilities and limitations unique to Airtable forms, some of which restrict your options. However, if you are using ‘form’ in a generic, non-specific manner — for instance, to mean ‘something I fill in using my computer’ — then all of the following comments apply. |
|
The easiest way to support pseudo-conditional logic would be through the use of linked records. For instance, in your example use case, rather than checking a box for ‘service dog’ and having the next few data entry fields change, the user would create a new linked record in the [ServiceDog] table. A window to this newly created record would then pop up, allowing the user to enter any service dog-specific data. On closing this window, the user is returned to the primary view and proceeds to the next triage question. Data from the linked record could then be made available (and visible) in the main [Triage] record through the use of lookup or rollup fields.
Whether this approach is suitable largely depends on how elaborately your triage form branches. If the branches are largely along the lines of the service dog example, where each optional branch offers additional information applicable to a subset of general population, linked records are an excellent method. If each fork in a branch leads the user down a substantially different pathway, without a subsequent return to a common series of data, you likely are better off doing as @AlliAlosa suggests and using a third-party form provider to front-end Airtable, at least for initial data entry.
