Short version: Why can’t airtable enforce unique entries for record IDs? This is an important feature and not having it is screwing me up. Long version: Continuing to spend most of my time working around Airtable’s billing policy. I’ve got a table where users will create work chits indicating they’ve worked x volunteer hours doing whatever. I’ve got 20 chit approvers and I really can’t afford to pay for 20 more users who will only doing approvals a few times per year. So, I’ve got a field in the Chit table that concatenates a URL which is then used to generate a link that goes in an email to the approver. When the approver clicks the link, it opens a new form for a new Approved Chit table and prefills the inputs with the values from the corresponding Chit record. I was really hoping to use the autonumber from the chit table to populate the Record ID for the Chit Approval table. My plan was to turn on unique enforcement for the Chit Approval table. But just realized that this feature doesn’t exist. My thinking was that by requiring uniqueness on the Chit Approval table, I would ensure that each chit can only generate one chit approval record. I’m not sure how to work around this one. Any suggestions mightily appreciated. But tired of spending all my energies to work around billing policies and really wishing that there was some policy based on usage rather than number of users. ... View more

Allow default values for field-types, AND allow the value in each record to be edited. Subsequent changes to the value of the default should either: A) Not be possible, to avoid data-overwriting decisions. Solution for a change: create a new field. B) Be possible, and overwrite the values that = the previous default value, BUT not overwrite the edited values ... View more

I’m trying to use a lookup function to help me avoid running a zap within zapier. But it seems I’m limited to do a lookup (count sum function) within a specific table, not within a specific view within that table. Here’s the deal… I currently keep track of my customers that have requested quotes from our shirt shop (but don’t have an actual order going yet) in a specific view within my ‘order’ table. When they convert their quote into an actual order, we just change the ‘order status’ within that specific record. In order to help each quote customer remember to reply to us (if they want to move forward or not), we automatically send them a ‘1 week reminder message’ and if they still don’t reply a ‘2 week reminder message’ - These messages are zaps running within zapier. These reminder messages are great and help us convert a lot of customers into actual orders, but sometimes we have an issue where certain customers call, email or physically come into our shop to start their order, versus going through our suggested route of converting their quote into an order. The problem that arises from them starting a new order while also having a quote with us is, even though they now have an active order record with us (displayed in our ‘all active orders’ view), they also still have an active quote record with us (displayed in our ‘all quotes’ view). Because they have two records for the same order, specifically the one in the quote view, we don’t have a way to check for conflicting records automatically and their ‘1 week’ and ‘2 week’ quote reminder messages will still be sent out (which is awkward when they have an active order at the same time). If I could do a ‘lookup’ function, and have it be limited to a specific view, I could do a lookup within our ‘all active orders’ view and have it count how many records exist, displaying a number. If this field displayed a number greater than 0, I could have our ‘quote’ order status records (that also have a number greater than 1 in the look field) show up in their own view. This view would then trigger an integration within zapier to auto-create a todo for our team to manually look into this, verifying if we need to delete the quote record or to see if it is, in fact, a unique quote. So, does this feature already exist and I just can’t find it? If not, I’d love to add it as a feature request. I can think of a dozen uses for this functionality. Thanks again! ... View more

I hope we can customize this layout similar to coda.io when you open the row record. ... View more

It would be helpful for repetitive data entry via a form if the new blank form “remembered” certain values from the last submitted values. Imagine taking inventory items in various rooms or containers. Instead of having to select that room or container every time you start a new form entry, it would save the user a lot of time if the previous room or container ID were persistent until changed. I envision a flag that can be set for each field when creating the form that indicates which fields will be remembered. Does this capability exist already? ... View more

Please consider adding the ability to change the standard icon next to each view. As well as create a group by view type option. For our use case having the ability to put our client’s logo next to the view that is filtered to their records would be so helpful for quick scan selection of the view we want to open. Also, we use views as processes that trigger integrated automation based on what view the record sits in. Being able to add some “stoplight” or process icons would be game-changing. ... View more

You offer no offline backups and all threads are closed vendors offering paid solutions. Downloading csv files not an option. When will you have a backup solution? ... View more

It would be great to see an option to add sections to the page builder. This could really increase the flexibility of the visual data on the page by having option of when to display that data if particular fields are empty. For example, you have a linked record that may not always get completed dependant on the task, but currently if you want to print that data you would have to set it up in the page builder anyway and print blank fields. By creating a section, you could drop a group of fields in there and select which ones need to be complete before this section will show. This would also work really well with larger invoices, rather than guess the number of lines you may need, the sections would push the lower order section down the page. Hopefully this makes some sense because it would be awesome to use… in my opinion 😄 ... View more

The scripting block is cool. But a lot of us use AirTable because we don’t know how to code. I’d love for someone to create an AirTable block (or feature) which would let me script automations through a Zapier-style interface. (no coding knowledge required). In my dream world, this would not only script automations within an AirTable base, but also between AirTable bases, and ALSO between AirTable and other software with API hooks. Also: it makes me grumpy to have to pay extra for Zapier. This should be a feature within the AirTable pro plan. ... View more