I’d find it quite useful to be able to embed and/or link to individual records. Ideally, this would be without sharing an entire table. ... View more

It’s great to be able to “Limit record selection to a view” when selecting a Linked Record, however, this means that the number of views gets out of hand quickly. It also means creating views that you will never look at (as they are only needed for filtering Linked Record options). I would prefer the ability to filter linked records by conditions instead. This would add flexibility and prevent the creation of unnecessary views. Bonus points if you could filter based on data from both the current record, and the Linked Record. For example, show if {Current record field} contains_______ and {Linked Record field} contains _________. ... View more

It would be very useful to be able to edit a lookup cell from either the source or destination table. Currently, if I’m working in a destination table and notice an error, missing information, or data that needs updating, I need to go to the source table and find the correct cell to edit that information. This is a challenge in a table with 107 columns! :bow_and_arrow: It would be much more convenient to be able to edit the information in the destination table and have the corrected information populate back to the source table. ... View more

I think this has been posted already, but I wanted to recreate the topic and give more details so more users can find themselves actually wanting the same thing. I’m sure many companies (like ours) fell in love with Airtable first they saw the great features it has. When you see how you can greatly simplify project, database, or table management in general, you realise that with Airtable you can save a lot of your owns or your employees’ time. But then… When I started to create some big tables, I found out this app lacks some simple regional options such as: Cannot change the decimal separator (not every country uses a “.” dot) Cannot set a custom date format (not every country in Europe uses MM/DD/YYYY) In Germany we use MM.DD.YYYY and this must be respected. I know there is a workaround to create another column and use DATETIME_FORMAT() formula to reformat the date from original column - but this is not a solution. Strings like month or day names should be translated to the chosen language of the base. So if you ever implement Regional and Language Options, please make it so users can change it for a base, and not whole program. So, before we migrate completely to Airtable, and switch to one of Business plans - we’d like these fundamental options implemented. Of course, we already are using Airtable, but just to create base concepts that we will use once this is implemented. Thank you for your time, and please make this a priority. ... View more

I’m imagining being able to access the data in a linked record in a similar way to how you access child properties of objects in many programming languages. Example You have an ORDERS table and a PRODUCTS table. PRODUCTS contains Item Name, Item Code and Price columns. The ORDERS table has a Linked Record field called Products. You could then access the Products properties within a formula field in the ORDERS table like this: Products.{Item Name} Products.{Item Code} Products.Price ... View more

As in other views (I.e., Grid, Kanban), I would like the ability to customize which fields are hidden/visible in the Calendar view. When embedding a calendar view on a website, ALL fields for each record are visible in the expanded view of that record. I would like the ability to select which fields can be seen in that expanded record via the “Hide Fields” function for Calendar views. Practical example: I am using the Calendar view on my website to show bookings for a facility. For my records, I have customer contact information tied to a record. However, I don’t want that visible to the public on the Calendar view. I only want the date/time fields and a few other select fields visible in that particular view. ... View more

Is there a way to add buttons which do some automated jobs inside AirTable ? This feature will be a killer. For example; From the customers table with form view, I click a button to invoice the customer and the invoice form comes with pre-filled info from the customer I was in and sends a mail with my smtp server. This can be done with a field type “macro button” added and some script added to the button ... View more

I think being able to lookup within a lookup of a linked field would be quite useful. For example, I have three tables: “Projects”, “Shipments”, and “Clients”. There can be multiple projects per client, and there can multiple shipments per project. I want to display the Client contact information on the “Shipments” table, but as the client name auto-populates using a lookup field, which pulls the name from a linked field on the “Projects” table, I cannot look within this lookup of a linked field. I can only get the desired result if I re-enter the Client data on the “Shipments” table via a linked field directly to the “Client” table, which is not only tedious but leaves room for error. If anyone knows of a better way to do this, please let me know. If anyone from Airtable can add this functionality, it would also be great. ... View more

It’s fantastic that the Airtable team is so receptive to feature requests. Realistically though, many of the requests now being made are for niche things desired by a small percentage of your userbase. I see many parallels between Airtable and Wordpress, particularly in how easy it can be for a non-developer to get up and running with a system that does most of what they need. It’s awesome to have such a robust API that lets you pull information out of Airtable really easily, but I get the sense that what a lot of users are after is a way to do more within the Airtable environment rather outside of it. I think Airtable is reaching a point a lot of these feature requests could be reacted to faster in the hands of third-party developers. A plugin library really could have the effect that launching the App Store did for the iPhone. Time and time again I’ve seen users in these forums saying ‘the lack of x feature is the only thing stopping our whole organisation from using Airtable’ and that seems like a shame to me. My instinct is that the key to success in this regard would be, much like Apple, to created confined spaces to innovate within. This would let the development resource at Airtable concentrate on: Ensuring full feature parity across mobile and desktop Higher level feature requests such as the ability to link between bases I would initially give developers four types of plugin that I’d allow them to create: 1. New base view type Example: Gantt, which could work for any record with two dates to function as a beginning and end) 2. New field type Examples Location (lat-long, address etc) Time (In pure hh:mm, rather than the time of day) 3. New record view type This could knock out all requests for designing a page for printing / reporting Developers could provide off-the-shelf templates, or users could roll their own with HTML/CSS. To keep tighter control, maybe avoid CSS altogether and restrict to Bootstrap and inline styling. Spaces for where data should appear could work using a shortcode system like Wordpress, something similar to a mail merge, or even something like Zapier’s recipe-building system 4. Base output This would give developers the ability to export the full contents of any view in a certain format, such as XML, that could be accessed through a HTTP URL. As the API has a rate limit on records that can be retrieved at once, this would be great for people with multiple hundreds of records in a base that only need to do anything meaningful with the bulk of the data a couple of times a day. Examples A plugin that would turn a view of products on sale into a Facebook Dynamic Product Advertising-compatible CSV file A plugin that would turn a view of products on sale into a Google Products-compatible XML feed ... View more