Status:
New Ideas
Submitted on
‎Jan 30, 2025
09:14 PM
Submitted by
Mike_AutomaticN
on
‎Jan 30, 2025
09:14 PM
List views within interfaces, and List page layouts do not support/show the sum of values of a given field (e.g. number, currency, etc). However, this is actually supported for grid views. -see comparison in image below. Even if something similar can be achieved using different workarounds as mentioned by @ScottWorld and @ATSolutionist in this other post submitted by @Scott_Brasted, a native out of the box solution seems completely needed. Mike, Consultant @ Automatic Nation
... View more
Status:
New Ideas
Submitted on
‎Jan 07, 2025
11:48 AM
Submitted by
Michael_Andrew
on
‎Jan 07, 2025
11:48 AM
I would be great if we could add buttons or links at the top of an interface sidesheets/full sheet record detail view to 'jump' to groups within the sheet. For record details sheets that are pretty long, this would be useful.
... View more
Status:
New Ideas
Submitted on
‎Jan 13, 2025
07:16 AM
Submitted by
MichaelSargent
on
‎Jan 13, 2025
07:16 AM
What is the proposed idea/solution? Somewhere within the Automations tab, it should show you how many automations you've created and how many are remaining out of your 50. Otherwise, users are forced to manually count how many automations they've created and then subtract, which seems completely unnecessary.
... View more
Status:
New Ideas
Submitted on
‎Jan 19, 2025
10:58 AM
Submitted by
oreocereus
on
‎Jan 19, 2025
10:58 AM
It'd be really use to be able to generate notifications for the user on the mobile app (or desktop). Seems like it'd be simple to do. We'd like this, as we have really complicated automations running, that are not 100% infallible to human input error. Currently I manage this with a "notification" single select, whereby if an input error has happened and needs to be fixed, it's tagged with the relevant issue. Input views are grouped by the notification select, so the user can at least see next time they open the app there was an error with their data entry. But this is messy, can create multi-day delays in getting information rectified, and also takes up 1 of the 3 "grouping" slots (and I already find 3 not quite enough). There'd be lots of reasons to notifcations would be useful to others. Obviously email and slack are options for generating notifications, but we're a small team (3) who work in the field together, so we don't use slack, and we're not checking our emails. Everyone prefers their email notifications to be left off, and to deal with their emails when back in the office.
... View more
Status:
New Ideas
Submitted on
‎Dec 02, 2024
09:30 AM
Submitted by
kuovonne
on
‎Dec 02, 2024
09:30 AM
What is the proposed idea/solution? In the configuration screen for a linked record field, show the name of the backlink field. This could be either read-only or editable. For same-table links, state that the field is a same-table link and does not have a backlink field. When creating a new linked record field to a different table, state that a backlink field will be created and display the name that will be used (or let the user enter a name for the backlink). How does is solve the user problems? Many novice creators do not realize that a back link field is created when they create a new linked record field. This would let them know. Once users are accustomed to the creation of backlink fields, some are surprised and confused when same table links do not have backlink fields. This would make things clearer for them. Creators often don't think about naming the backlink field, as the default name usually works when there is only one linked between two tables. However, sometimes the default name doesn't work and should be changed, especially when there are multiple links between tables. Showing the name reminds creators to pay attention to the backlink field name. When deleting a linked record field, the backlink field also often needs to be deleted as well (versus hanging around as a single line text field). Showing the name of the backlink field will make creators more aware that they should delete the backlink field, and also make it easier to find the backlink field to delete it. When there are multiple links between tables, especially in legacy bases where backlinks were not named well, it can be difficult to figure out relationships. Although the Base Schema extension shows which linked record fields go together, in a large base, the diagram is a huge tangled mess and too hard to work with. It is also possible to identify backlinks by looking at field data, but this is cumbersome and depends on knowing the data values or having the ability to put in test data. The "Show Dependencies" tool lists the backlink field among all the other field dependencies. This is probably the easiest way to see the name of the backlink field, but the nature of the dependency is not obvious to new users. Scripting is another way of identifying backlinks, but that is also a niche skill. How was this validated? Personal experience maintaining bases. Who is the target audience? People with creator permissions who will be creating and maintaining linked record fields, including both novice and experienced creators.
... View more
Status:
New Ideas
Submitted on
‎Dec 25, 2024
01:59 PM
Submitted by
Sherman
on
‎Dec 25, 2024
01:59 PM
The Free Version of Airtable continues to be degraded to the point that it now feels more like a trial than a free option. The addition of an annoying pop-up to subscribe is my last straw. I am not a free user. I've been a fan of Airtable for many years, introduced it to hundreds and interacted with thousands through many different use cases I've created. I'm such a fan that I've talked with everyone from teens to top tier executives in showing them how Airtable could be of use to them. I've created bases for countless people, most of them business owners. As a business owner myself I enjoy what I've been able to do and love showing others what they can do. I've stopped doing that. The free version of Airtable has become so disagreeable and degraded that I don't feel confident I can do something worthwhile to demonstrate its use. The last time I really showed Airtable to someone I promised big and failed completely. I bought a couple rats from a breeder and had some quick thoughts on how to make tracking her lineages and sharing rat pictures online easy with Airtable. I asked if she'd like me to put something together and she was enthusiastic to see what I suggested. I failed completely. Linking bases had been disabled in the free version had been removed since the last time I tried it with the free version, and I couldn't find a workaround to make my vision reality. So, I dropped it, and she went with something else. I haven't tried since even though I'm always thinking of ways to make stuff for other people. Airtable competition isn't where I want it for my use, but it's getting there. From now on, when I want to show someone an idea for a way to make their business smoother, I won't be doing it with Airtable. I'll be showing them the competition and maybe saying that I could do it a little better with a paid Airtable account, but that won't be their introduction to the format. Please reconsider chasing people away from free accounts. They used to be awesome, now they're terrible. I was a free user for months before I decided to become a paid user, and then a paid user for many years and more importantly, a fan who shared the product with countless others. Just something to consider.
... View more
Status:
New Ideas
Submitted on
‎Jan 07, 2025
05:17 AM
Submitted by
Mike_AutomaticN
on
‎Jan 07, 2025
05:17 AM
What is the proposed idea/solution? Linked Records, Lookups and Rollups are currently sorted in the order in which the linked records have been linked. However, this is many times not enough, as we need a different way in which to show the data! The proposed solution is to have a sorting feature within the lookup (or even linked record, or rollup) to show the data differently -e.g. alphabetically. How does is solve the user problems? Will allow users to show their data in a way that makes more sense to the end user. How was this validated? Multiple Community Posts requesting for help/guidance on how to sort such values (which they actually cannot)! Who is the target audience? Users with specific needs on how data is displayed. Mike, Consultant @ Automatic Nation
... View more
Status:
New Ideas
Submitted on
‎Nov 28, 2024
03:57 AM
Submitted by
Mike_AutomaticN
on
‎Nov 28, 2024
03:57 AM
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
Status:
New Ideas
Submitted on
‎Nov 18, 2024
03:15 AM
Submitted by
Fabian_0904
on
‎Nov 18, 2024
03:15 AM
What is the proposed idea/solution? Add a Feature so you can change the background color of cells and whole colums manually or based on condition matching. How does is solve the user problems? Design of Tables and List Views will get more clean and easier to use / navigate. Also Users can color cells based on their content (like positive=green, negative=red, ...) How was this validated? It's basic visual Design theories. Who is the target audience? Nearly everyone, at least every user who needs to navigate through big airtable bases & list views.
... View more
Status:
New Ideas
Submitted on
‎Mar 06, 2023
12:27 PM
Submitted by
Sara
on
‎Mar 06, 2023
12:27 PM
What is the proposed idea/solution? I would like to share an interface with a person that hasn't an Airtable account. How does is solve the user problems? In this way people without an account could see only that interface (not the base) through a link. Who is the target audience? All people that work with external customers. A lot of people commented about this idea here: https://community.airtable.com/t5/interface-designer/how-show-an-interface-without-airtable-account/m-p/144399/highlight/true#M1257
... View more