@marks I'm still a little new to Airtable, so I just want to make sure. Is having the recordid in the URL the privacy concern? Thanks!
Hiu @rafaban9811 - the potential privacy implication is if you hide a linked record field and would consider the list of records in the linked record field to be sensitive information. For example, hiding a list of client names (or even a list of IDs would leak your client count).
Instead, I'd recommend you create a new single-line text field called "Client Record ID" and use that on your form to prefill the Airtable record ID (recXXX) and optionally hide it too. Then, have an automation that is triggered by form submission that copies that record ID in the "Client Record ID" field into the linked record field. This way, even if your user unhides the "Client Record ID" field on your form, they just see a single client record -- not the ability to list (or count) all your clients.
@marks ok thank you, that makes sense!
So if the use case only has one person (the person using the form) in the linked record then prefilling the linked record with the ecodeUrl(recordID()) wouldn't compromise security of the base? The issue is if you have many records in the linked record field people would be able to see the list.
Thanks,
@rafaban9811 I cant comment on "compromise security of the base" but the principle I recommend following is assuming people who have access to your form are curious and tinkerers. Therefore, make sure anything you hide using URL params is not something you wouldn't want them to see or be able to change in a way that would negatively impact your work.
Hope this helps!
This new feature breaks URL links due to the 2 underscores at prefill_ and hide_ . I am trying to place my URL in an <a href" 'URL' "><img <a/> code in automation email message body. Can anyone help to figure out how to escape markdown from breaking this URL. I can't use a simple backslash because the URL will then be an incorrect URL with added '\' backslash. So I need another option. Silly IMO to use 2 underscores when airtable knows that anything inside _test_ becomes italicized. Any solutions?
Great. But, when will we be able to hide the form TITLE? When embedding forms, that is a huge issue and quite frustrating. Especially if we have two of the same form - one to email, and one on the site. Both named the same unless we add 'Web' and 'Email' to our form name, which of course then appears in the customer's view of the form. Yikes, fix this already!
@marks did the new form builder break this feature - i can't get it to work anymore
Hi @andylpage95 - you can hide fields using Interface forms. In your example, change "hide_visable=yes" to "hide_visable=true".
I believe you should be able to continue using "legacy forms" as well, but I recommend trying to use interface forms going forward.
ah i see, so it looks like to prefill AND hide a field, i'd do
hide_visable=true&prefill_visable=test
to set visable = to "test"
The hide_* parameter should always be true/false. While related, the two options act pretty independently
