Hmm I just tested this out with a prefilled form link and it worked fine; the prefilled data showed up in the table

Is that field hidden by any chance?

I made it hidden with a condition, once a customer fills out the first required field I have it go away. I don't want it showing on the form as the customer doesn't know what the source means and I am trying to avoid confusion. Would that mess it up? 

Yeah, hidden prefilled fields aren't submitted I'm afraid.  As a workaround, perhaps you could try hiding it via the URL params instead? 

In the following link, we've prefilled the "Notes" field with the word "Test" and hidden it:
https://airtable.com/appnuKCRJRdYCmdHp/shr4yTavN1qCmLga8?prefill_Notes=Test&hide_Notes=true

And after you submit it you can see the new record here, and you can see that the "Notes" field is populated

This method also works with Interface forms.  The downside to this is that the user is technically able to unhide the field and modify it by editing the URL though

Yes I have this issue too. I’m trying to make a form, to update a table.

For this purpose I need a Record ID. For the form to look neat and clean, I am hiding Record ID. But as soon as I hide the field, it is not updated when the form is submitted.

I’ve seen this is the problem for a longer time now. 

I’ve also tried to hide the field with URL parameters. Result is the same. Do programmers have any kind of update on this issue?
These steps are also described here, apart from the hiding a Record ID field. https://support.airtable.com/docs/updating-records-using-a-form-in-airtable#use-case-example-when-updating-records-using-a-form

​@Alioness 

Unfortunately, that is not possible with Airtable’s forms.

Your best bet is to use Fillout’s advanced forms for Airtable, which lets you both prefill & hide fields — and the fields will still be submitted.

And even better:

With Fillout, you may not need to prefill at all (depending on your use-case scenario), because Fillout allows you to update Airtable records directly with a form.

Fillout is 100% free, and it offers hundreds of features that Airtable’s native forms don’t offer, including the ability to update Airtable records using a form, create custom PDF files from a form submission, accept payments on forms, display Airtable lookup fields on forms, create new linked records on a form, control access to a form via SSO or email domains or a list of email addresses stored in Airtable, perform math or other live calculations on your forms, collect signatures on a form, create multi-page forms with conditional paths, connect a single form to dozens of external apps simultaneously, add CAPTCHAs to your form, and much more.

I show how to use a few of the advanced features of Fillout on these 2 Airtable podcast episodes:

• Using Fillout to create an eSignature approval process with PDF file creation.
• Using Fillout to create an order entry form with line items.

Hope this helps! If you’d like to hire the best Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld

Hm I just tried the URL to hide the prefilled field and that worked fine.  Could you provide an example of your link?  

Here’s the one that works:

https://airtable.com/appnuKCRJRdYCmdHp/shr4yTavN1qCmLga8?prefill_Notes=Test&hide_Notes=true
 

I just took a wee bit of time to record and recreate everything step by step, showing that when I hide a field through the form it doesn’t make a record. Then I published a form with non-hidden field and showed that everything works fine. And of course I wanted to prove my point and changed the URL like you said. Then for the my surprise - IT WORKED!!!

I guess when I was trying to solve this issue yesterday, I forgot to publish a change in Form, where the fields are NOT hidden, but i did only URL update. I didn’t notice this mistake before I tried to prove my point and record everything. 😂

I even did all the Fillout forms as a workaround yesterday. Which of course works just fine, but I had to dig up the URL parameters to do the trick, because I have hundreds of people who gives me back feedback and the prefill is dynamic, based on Record ID. That data is then filled into the Mailchimp, so it everyone updates his own record.

I must say - you saved the day. Thank you. 😊

​@Alioness 

When you use .Fillout’s advanced forms for Airtable, you don’t need dynamic prefill links.

No URL parameters, no constantly-changing links, no formulas that calculate incredibly long links, no automations, none of that.

That’s the beauty of Fillout.

With Fillout, each Airtable record gets ONE STATIC & UNCHANGING URL LINK THAT NEVER CHANGES.

So everybody can keep clicking on their same link, and continue updating their Airtable record.

You can learn more about this here:

• Update existing Airtable records with a form

I also demonstrate how to do this on this Airtable podcast episode:

• Using Fillout to create an eSignature approval process with PDF file creation.

Hope this helps!

If you have a budget and you’d like to hire the best Airtable consultant to help you with this or anything else that is Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld

Nice to share this, thanks. 😊It’s very useful. However I have a wee bit of specific needs. It’s like I ask people:
Do you want to postpone membership? The answer on Fillout is explicitly yes and it goes like it is in the Airtable. Here your proposition comes in handy.
Then later I ask:
Do you want to reactivate the remaining time of membership? The answer on Fillout is again explicitly yes. But it must be transformed into no in the Airtable. Here the automations comes in and the URL “hocus-pocus” :D 
In Airtable I have then a column that says “postoponed” and there I get default value no, then can be changed into yes and at the end again no.

Thank you for the link, it’s good to know all those interesting solutions.