Zapier has a similar function to the above, editing with a duplicate table
I’m also looking forward for such a feature!
In our case I’m looking for a simple way to manage our lab inventory as we have many students that borrow and return equipment, by themselves, so I’m trying to find a simple way for them to select the item they are borrowing from a drop-down list for example or start typing the item name with an autocomplete, then type their name and submit the form, thus updating the database, there is no need for them to see the entire table.
Agreed. We are also using Airtable as our Makerspace management solution and it would be extremely beneficial to have a read-only type form where students could edit their own reservations within a calendar view or through a form. Currently we use a clunky scenario in Integromat to do this, but it just makes so much more sense to have a read-only (non-paid) type account for people who only need to edit their own records. You’d probably have to create a “Record Created By” field though. Then rather than users being records in the base, they could be read-only collaborators in the base and have their own “profile” of machine reservations.
I have been working on building functionality to allow forms to edit data on Airtable — to make this work I’ve made a portal product called Airportal (https://airportal.app) so you can design forms that work with your existing data.
We are collecting people for the beta launch of this product in the next few weeks. Sign up at the link above if you’d like to be part of it.
@Sam_Davyson, this looks awesome - I’ve already recommended it in some threads.
Question - I’m guessing that to create a platform like this you had to isolate the app from the Airtable API in a way to avoid rate limits. I don’t want to know how you did it - just to confirm that you did before I widely recommend it.
Also curious why you didn’t give it a cooler name like …
Thank you so much @Bill.French!
I think Airportal is a pretty cool name! It is like Airport-al
Re: the platform limits, yes we are implementing a caching layer to avoid any issues with the rate limits for popular portals.
Yeah, it’s not bad, but the marketing guy in me always leans toward two syllables whenever possible.
It would be very useful to add an Airtable form to Edit existing records where the editable fields could be restricted much like the hide/unhide fields in the form that allows adding records.
Is Airtable placing this in a future release?
I agree with the posts here as well. This is an essential feature to make use of Airtable.
I am in the process of setting up a Project Management system via Airtable and, I have to say, I spend more time here, scrolling through pages and pages of what seem to be obvious need feature requests, that it worries me. The idea was that this would be a quicker set-up than building in MySQL from scratch, at least, that is exactly how Airtable are marketing their product. The issue I have is that, in general, it seems that there is little to no interest in the community or its needs.
Was this issue ever solved? It certainly does not appear so, along with so many others.
I guess that my questions are these:
- Did this ever get implemented?
- Do feature requests generally get implemented?
If the answer to either of these is no, then this is a deal-breaker for me and, sadly, I will abandon this project and go back to MySQL. Not necessarily for this one feature, but for the general lack of forward motion that I see everywhere in these forums.
No, that’s not a solution to my use case:
We invest in start ups. When we first discover a company we input roughly 30 fields of data. If we there is an opportunity to invest we will input another 100 fields. If we decide to invest there are another 50 fields.
I need to be able to send out 3 forms for different life stages of the record.
LOL. I just read my post from six months ago and realized Airportal has been renamed to a two-syllable word. Called it!
We made a tool that allows you to edit records using Airtable Forms. We solved most pain points in some existing solutions:
- Form fields are pre-populated with the existing data.
- Records are updated instantly after form submission.
- Form requires minimal setup (no need to match multiple tables/fields/select options)
- Supports limiting linked record selection to a view.
^This last one can only be made possible by using Airtable’s native form.
I’ve been helping a user that would benefit from a multi-row editable form as well. The user would like to share a selection of his data for review from judges, but those judges shouldn’t see each others’ responses. In other words, a judge would be editing multiple rows of data, but shouldn’t see all available data.
Many thanks for sharing my requirement Zollie - yes, there are significant overlaps. As a comment, I’d add that there’s a significant difference between using a form process (where you need to identify the record to be updated) and a view process (where you browse records and update one or more fields). The advantage of views IMO is that (a) Airtable already supports them, including the ability to hide certain fields and (in beta) lock the edit permission for others (so you can display them in an expanded record but not update them) and (b) they permit browsing and very rapid data updating. For example, if I could edit records from a Kanban view, a judge (to use my use case) could scroll through records, rapidly assigning a data value from a selection by dragging each record to the appropriate column.
[obvious edit] - to do this, you’d need to (a) be able edit from a view and [b] be able to share that view without granting access to any other views or tables.
On this page I have described how you can easily overcome the missing feature with Update Forms.
Second I have also described how to create a Custom Portal for Airtable so that even non Airtable users are able to see a Base, View and even Update, Delete and Create records.
Worked on this solution for at least couple of weeks. Really curious about your feedback