Forms and Lookup Fields

I want to use a form to request entertainers. In the base, I have a lookup field for Event Contact (looking up in the Event Contact table). My problem is that when I put the Event Contact field on the Form, the requester can see all of the current contacts. I would like them to be able to enter their name without seeing other contact names.
Is this possible??

I have the same question - I want to add a lookup field to a form. Is there any information on this anywhere?

Hi @Rebecca_Glaser and welcome to Airtable Community :smiling_face_with_three_hearts:

@Santa_Bill_Gross - I’m terribly sorry to see that your question went unanswered.

There’s only two solutions that I can think of.

The first being that you create a regular field and link that one to the form and allow the users to enter their name there. After they submit the form, you would then go in and update your original field with the correct name. It’s manual, but it will keep things confidential.

The other option would be to integrate Airtable with another form building application such as Google Forms.

Airtable’s forms are simple and basic and don’t always provide the solution that some people require.

I’m sure this wasn’t the answer you were hoping for. :sleepy:

When you say create a regular field - can you please expound - where do I create regular field - I am not sure I understand this what you are saying

The issue involves the way Airtable handles form views versus grid views.

  • In a grid view, records are created and updated in real-time: You add a row to the base, Airtable creates a new record and assigns it a RECORD_ID(); you enter a value into {Name}, and the {Name} field in rec1234NewRECORD5678 is updated.
  • In a form view, values are held in the browser until you click ‘Submit form’. At that point, Airtable checks to make sure all required fields have data; if so, it then creates a record and enters all of the provided values.

This latter all-at-once mode allows form users — who are more likely to be casual or one-off users — to change their minds ('I’m not going to give this ^%$#! my phone number!), return later with information they were lacking ('Did Mom want to extra-large or the jumbo?), or abandon an entry ('How did I get here?) without cluttering your base with partially or invalidly filled records.

Unfortunately, it also obviates any Airtable action based on the current value of a field — such as directing linked-record lookups to a view filtered according to the value of another field in the record being created, as is possible with grid views


  1. I’ve not tried it, but conceivably one might be able to do something using a two-form solution through a clever system of redirects. I rarely use forms, though, but perhaps someone with more experience in that area can chime in…