Dec 09, 2020 05:41 AM
I’m new to Airtable, and have been browsing the help center and playing around with the features. One thing I didn’t see mentioned anywhere was input validation. For instance, for a numeric field requiring the value to be less than, greater than, or between values-- as an age field which must be 21 or greater. Or a date field which must not be a future date. Or a currency field limited to 10000. An so on.
How would these be done in Airtable ?
Solved! Go to Solution.
Dec 09, 2020 09:37 AM
Welcome to the community, @Shmuel_Preiszler! :grinning_face_with_big_eyes: In-field validation isn’t currently available in Airtable. The only way to pseudo-validate inside of Airtable itself is to provide feedback in another field using a formula. However, this won’t work with forms because formula fields can’t appear in forms, and Airtable forms also don’t provide native validation options. Another option is to use a third-party form tool like JotForm, which can validate input before the data is sent to Airtable.
Dec 09, 2020 09:37 AM
Welcome to the community, @Shmuel_Preiszler! :grinning_face_with_big_eyes: In-field validation isn’t currently available in Airtable. The only way to pseudo-validate inside of Airtable itself is to provide feedback in another field using a formula. However, this won’t work with forms because formula fields can’t appear in forms, and Airtable forms also don’t provide native validation options. Another option is to use a third-party form tool like JotForm, which can validate input before the data is sent to Airtable.
May 12, 2023 08:39 PM
We built an input validation solution in miniExtensions Form. You can set it to validate against another formula field in your table or even use Regex. Here's a condition example where 'Age' is required to be 21 or greater.
Oct 07, 2024 09:36 AM
Hey @Shmuel_Preiszle ,
Airtable doesn’t have native input validation like setting limits for numbers or dates, but you can use the DataGuard extension for that. It lets you set rules like minimum/maximum values for numeric or date fields, so you can enforce things like an age of 21+ or restrict future dates.
It’s a good way to keep your data accurate from the start.