Skip to main content
Solved

Hide record ID not working in form prefill.

  • February 6, 2023
  • 3 replies
  • 43 views
A
Forum|alt.badge.img+9

I am trying to follow this video tutorial: https://www.youtube.com/watch?v=BkAY7OHEgdc

The formula:

 

'https://airtable.com/shr12G6XKocbeGi0H'&'?prefill_Doll%20ID='&RECORD_ID()&'&prefill_Doll%20Name='&ENCODE_URL_COMPONENT({Doll Sculpt})&'hide_Doll%20ID=true'

 

However, the part to hide the record ID is not working. This is what happened to the form:


As you can see, the "Doll Name" area has the formula to hide the record ID in it. 🤔 🤔

 

I tried doing it exactly like the video and only having "(Doll Sculpt)", but it said there was an error with the formula and I was forced to use "({Doll Sculpt})". Could this be the issue?

I haven't even tested the functionality (I haven't set up the automation) of this yet because I have hit the snag listed above. 😥

Thanks for reading!

Best answer by marks

Looks like you want to change

&'hide_Doll%20ID=true'

to

&'&hide_Doll%20ID=true'

The first & is for the Airtable formula to concatenate (combine) the components and the second & is to go into the URL

Airtable Account: Free PlanRecords: 1,200/1,200 1000/1000 (I might have to find a different solution soon)Automation Runs: ??/100Extensions: 1/1 (TinyPNG Compression Script, looking for free alternatives)

3 replies

M
Forum|alt.badge.img+13
  • marks
  • Inspiring
  • Answer
  • February 6, 2023

Looks like you want to change

&'hide_Doll%20ID=true'

to

&'&hide_Doll%20ID=true'

The first & is for the Airtable formula to concatenate (combine) the components and the second & is to go into the URL

A
Forum|alt.badge.img+9
  • Anxious
  • Author
  • Inspiring
  • February 6, 2023

Looks like you want to change

&'hide_Doll%20ID=true'

to

&'&hide_Doll%20ID=true'

The first & is for the Airtable formula to concatenate (combine) the components and the second & is to go into the URL


Fantastic, that worked!

However, I tested this out with the automation and realized that it deleted the original table data if the relative update form field is left blank, which makes sense since it directly replaces all the data in that record. That won't work for me, so it is back to square one.

I could prefill ALL the data, but this is a massive table with photos and linked records, so that may not work.

Airtable Account: Free PlanRecords: 1,200/1,200 1000/1000 (I might have to find a different solution soon)Automation Runs: ??/100Extensions: 1/1 (TinyPNG Compression Script, looking for free alternatives)
M
Forum|alt.badge.img+13
  • marks
  • Inspiring
  • February 6, 2023

Fantastic, that worked!

However, I tested this out with the automation and realized that it deleted the original table data if the relative update form field is left blank, which makes sense since it directly replaces all the data in that record. That won't work for me, so it is back to square one.

I could prefill ALL the data, but this is a massive table with photos and linked records, so that may not work.


Hey @Anxious - I'm glad that helped!

And yes, you're right. I am not 100% sure of the cleanest way to handle that in the UI (in the API, this is the difference between a PATCH and a PUT request). Off the top of my head, if you are adding these new records into a new table, you could have a formula that looks at the form submission versus the previous record (via linked records) and then return the original value if the form submission's value was left blank. This would not allow people to empty a field via the form submission without some special-case'd keyword like "empty" or something and then working that into your formula logic.

I'd recommend maybe starting a new thread on that topic to keep things clean and searchable in the forums!

Terms & ConditionsAccessibility statement