Skip to main content

Prevent creation of blank records in a table


Would it be possible to make it impossible to create blank records in Airtable - it’s so easy to create these that bases become littered with them. It’s even worse if you accidentally add a record in a grouped view because linked record are created which are otherwise blank.


One way to do this would be to give the user the option of making one or more fields ‘required’ - and without them the record would not submit.


I find having to constantly delete such empty records quite annoying!

46 replies

Just a suggestion - I also run into the problem, so I filter empty records in my key views and have a view that shows just blank records which can easily be removed every once in a while… whenever I notice blanks in linked records becoming a problem, I go through my tables quickly and “clean house”. Maybe not ideal, but should work until they make a magic button…


  • Known Participant
  • 51 replies
  • August 7, 2017

I think this problem is a real weakness of the AirTable interface, in grid view. The silly thing is that Airtable has already solved this problem in every view type EXCEPT grid view. ALL the other view types employ a big giant button (in the bottom right of the window) to add new records. That makes perfect sense, and makes it almost impossible to accidentally add a record. I don’t know why the same mechanism isn’t used in Grid View.


I agree with this problem. It particularly problematic if you have an auto-number field because by deleting the blank records, you “break” the numbering of the records.

An idea could be to have a choice in the table or in the view to choose the way to create new record

Ex. View x from table Y: prevent automatic creation of records (Activ/disabled)


  • Known Participant
  • 11 replies
  • August 8, 2017

I absolutely agree with this. I have multiple people putting data into our data base and they frequently create blank records that I then have to go in and delete. I would appreciate this usability upgrade immensely.


  • Known Participant
  • 44 replies
  • August 8, 2017

Yes, this is annoying, especially when I’m in a filtered View and the new record disappears because it is filtered out.

I can’t delete the blank record unless I unfilter the current view (something that I don’t want to do) or I go to another view that displays the blank record, and then I delete it and then go back to my filtered view. Or, I can choose to ignore the newly-created record(s) with the intention of doing my clean-up later, in which case I’m sometimes surprised at how many blank records I’ve created.


I like the blank records in my tables - I’d hate to see them taken away completely.


Was just looking for the ability to disable auto-creation of blank records. Would be great to get this feature added.


Perhaps the best way to deal with this is to enable no more than one auto-created record via this feature, meaning if a blank rec is already at the bottom, don’t create another one.


  • Participating Frequently
  • 5 replies
  • September 3, 2018

Can I bump this? It seems like it would be an easy fix and I’m sure everyone who’s ever used Airtab;e has run into this problem at least once. I however seem to delete empty rows every day.


  • Known Participant
  • 29 replies
  • September 4, 2018
Michael_Crinni1 wrote:

Can I bump this? It seems like it would be an easy fix and I’m sure everyone who’s ever used Airtab;e has run into this problem at least once. I however seem to delete empty rows every day.


Double bump.


I use Airtable on a daily basis and, despite my efforts to keep it clean, am constantly deleting empty records created inadvertently by myself or another team member.


I know not having a submit or save button speeds things up on the front end, but it slows things down on the back end, when I have to go through and clean house.


I’d still like to see a proper solution for this - but there is now a possible way to automate the house keeping at least. With the latest update to the Integromat link to Airtable, you are now able to create logic to delete records from your Airtable base.


A very simple search records app which finds the records:



followed by an app which deletes the records returned by the search is all that’s required:



Remember to set the max records figure in the first step to a large enough value to return all the possible blank records and then the second step will run for all the records found.


You can then set your scenario to run as often as you want - or set it to run overnight for example.



  • New Participant
  • 1 reply
  • June 12, 2019

Yes, this is very annoying. My team and I are using it daily and I would say that this our biggest issue.


You could make a blank cell view that filters everything but blanks and just delete all the records in the view every once in a while…


  • Participating Frequently
  • 7 replies
  • June 15, 2019

There are solutions for removal of them once they are created as per above suggestions, but we have a table with autonumber being used for sequencing and for audit purposes we prefer there to be no gaps in the sequence. This very issue causes the most reasons for gaps. The other reason is not being able to restrict some users from the ability to delete a record 😦


Michael_Berman wrote:

You could make a blank cell view that filters everything but blanks and just delete all the records in the view every once in a while…


We literally have a script that runs against such a view and flags blank records as “ghosts” 👻


It’s a dumb workaround that still requires human record deletion or repurposing of ghost records with “old” record IDs.


Bump, Bump & Bump Again.


This is our single biggest frustration with Airtable - An otherwise brilliant product.

The option to only create a new row on “Double Click” would resolve this neatly.


  • Known Participant
  • 54 replies
  • July 8, 2019

Bump bump bump too! You should be able to define views where new line records cannot be added in that view.


Is there a solution for this yet? if not bump!


+1. I’m using an Autonumber to create unique IDs for each record, and having it being incremented each time someone clicks the row by mistake is annoying.


  • New Participant
  • 2 replies
  • October 10, 2019

Bump! I’m about to train my team and anticipate that the accidental creation of records will be our biggest issue. I’ve been using Airtable for a month and haven’t been able to avoid accidentally creating records every single time I use the (otherwise brilliant) interface.


  • Known Participant
  • 13 replies
  • December 11, 2019

Yeah this owuld be nice to fix, annoying having to clean house all the time.


Same frustration here ! Please do something…


Just want to add our name to this list - we are about to move a large system into Airtable and I can already see the autonumbering of blank records being a problem! Please add some way to disable creating records through the Grid View click, or ability to limit only certain users from creating records in a table. In the table we’re working with, we only want the API to create new records.


  • Participating Frequently
  • 8 replies
  • January 11, 2020

Me too. In my case, empty records break the R package that I use to import data via the API.


Russell_Bishop1
Christoff wrote:

Yes, this is annoying, especially when I’m in a filtered View and the new record disappears because it is filtered out.

I can’t delete the blank record unless I unfilter the current view (something that I don’t want to do) or I go to another view that displays the blank record, and then I delete it and then go back to my filtered view. Or, I can choose to ignore the newly-created record(s) with the intention of doing my clean-up later, in which case I’m sometimes surprised at how many blank records I’ve created.


Also - if you ‘Undo’ the action, you can’t see proof that you deleted it because you couldn’t see it in the first place. Usability nightmare!


It seems that Grouping by a Computed Field prevents to add any new record.

An unpleasant solution could be to group all records on one unused computed field.



Downside : You cannot add new record from this Grid view anymore.


Reply