What is the proposed idea/solution? Allowing forms to create NEW linked records, rather than only allowing to select from a list of already existing linked records. In other words, the ability for a form to have its Parent form submission, and one or multiple Child form submissions (for the linked records). See Fillout's solution as an example. Dummy scenario: If I want to submit information for a Family (Family table) and for the members of the Family (Members table) which can be one or multiple, I would not be able to do this from only one Airtable Form. I would need to submit one form for the Family information, and separate forms for each Member. How does is solve the user problems? Would avoid having to integrate different softwares, build dirty automations, or handling re-directs, just for the sake of creating linked records. How was this validated? This issue comes up with plenty of my clients, multiple questions have been asked on the Community on how to handle this, and it has been a topic of discussion with fellow builders and consultants. However, I'm not sure whether it has been actually submitted as a "New Idea"/Feature Request (if it was already, I'm super sorry -however it might be useful to bring it up again!). Basically, Airtable forms do not allow to create NEW linked records from the form itself (i.e. we can currently only select from a dropdown of already existing linked records). There are obviously several different workarounds such as: (i) using other form softwares (e.g. Fillout which I really love, but is still a pain to need additional integration just for this); (ii) handling the creation of new linked fields from interfaces rather than forms (i.e. would mean treating the interface itself as a pseudo form); (iii) having temporary fields on the main table which are only used to push data via an automation for the creation of the linked field (super dirty solution which I would almost never recommend); and (iv) others. However, all of those solutions are far from ideal. Who is the target audience? Airtable users who need to capture information via forms for a base with multiple linked tables (I'd say almost every Airtable user). Thanks!! ... View more

Good day Airtable overlords, I love the ability to be able to include Text boxes with headings for sections on an interface page.  It's nice to be able to include paragraph text below, which I use for instructions for users, but I'd love if that smaller text could instead be more like a field description, ie a hoverable "i" associated with the text box.  Currently the text box just shows as "Untitled", with "No configurable properties".  There are three dots to change the name of the text field, but clicking on "Rename" actually does nothing.  It'd be great if we could just add help text to the text field, so that we can use the text field as a section header, and the help text doesn't have to take up valuable real estate.   Your loyal servant,   Craig ... View more

What is the proposed idea/solution? Airtable desperately needs more options for date filtering. Most importantly the following: within next calendar week/month within past calendar week/month on or before the end of this calendar week on or before the end of next calendar week Airtable barely has filters for calendar weeks which is extremely frustrating because most program managers are looking at the tasks for the given week and it is super annoying to have to make it a custom between 2 date fields because saying on or before one week from now will show tasks from the following week within the first few days. How does is solve the user problems? This makes searches more automated so they will automatically show you what is happening in the given calendar week/month without having to do the current way which is: Date is on or after 11/1/2024 or date is on or before 11/30/2024 (which has to manually be changed every month). It just makes things unnecessarily difficult when it should just be simple to add these date filters.  ... View more

Nested records don't currently have a great way to view, as the list view hierarchy only supports nested records in some contexts, and has a limited number of levels shown when it is supported. Implement a view or add to an existing view (e.g. list) the ability to have nested records of the same type and infinite (or at least more) levels of nesting displayed. The ability to fold nested levels to better navigate the list would make this very manageable for large datasets with several layers of nesting.  ... View more

What is the proposed idea/solution? The org chart extension is a great tool to visualise a tree of records where there is a parent/child relationship implemented using a linked field to a record of the same type. However, the extension isn't easy to integrate into an interface and there is no good way for an end user to choose which group of records should be visualised.  How does is solve the user problems? Adding the visualisation to interface designer integrates this data view into interfaces and could provide the end user some control over what records are displayed in the visualisation ... View more

What is the proposed idea/solution? to avoid needing to use automations to populate a record when clicking a button, allow the 'update record' action to use dynamic values as you can currently do using automations. How does is solve the user problems? As the number of automations is limited to 50, this avoids needing to use trivial automations to capture dynamic updates to a record, for example setting a date/time field to the last modified time to note when a change was made, or copying user provided text into another field. ... View more

What is the proposed idea/solution? I use the Timeline view to plan staff resourcing, and I need to see when weekends are so that we can plan around them. The single letters representing days are very small, and visually it takes very intentional cross-checking between the entries and the records and the days on the timeline at the top, which makes the process a lot more fiddly. Currently, the only way to do this visually in the way I'd need it is to create a record for a weekend and colour it based on the day of the week and tag it in every swim lane, however, creating an empty record purely for a weekend could potentially cause data issues. It'd be easier if we had the options to colour dates on the UI. How does is solve the user problems? People could track regular deadlines, weekends, public holidays etc on timelines without the need to create a record (potentially causing data issues) to do so.  ... View more

Some buttons can have rules applied to them so that they only appear for certain users, for example. Other buttons don't, like top-level 'view' buttons. This means I still have to duplicate interfaces to provide differing levels of access. Please enable 'Visibility Rules' for all buttons in interfaces. See attached image of where this configuration could go. ... View more

What is the proposed idea/solution? The light greyblue linked record background in the List View on Interfaces makes me sad.  Maybe make the grey take up the whole field, like a Large view of a Single Select field? Or maybe just transparent? I think something different would really help with the wonderful dropdown selection window. How does is solve the user problems? It takes out the sadness of the dreary grey and replaces it with the joy of not-grey. Who is the target audience? Look at that grey and tell me it doesn't make you sad. If it makes you sad, you're the target audience. On a more serious note, I totally get that this is unlikely, as it's probably more a UI consistency thing, but by golly I resist with every fiber of my being using linked record fields on List View because of how they look.  ... View more