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
‎Nov 30, 2024
02:44 AM
Submitted by
palagrandintok
on
‎Nov 30, 2024
02:44 AM
What is the proposed idea/solution? I use the timeline view to plot upcoming translation projects and see what resources will need to be allocated to them over the coming months. I would love to be able to have the bar on the timeline change height depending on the size of the project, so I can see at a glance how much work each project represents. In my case, this would simply mean referring to a 'Number of Words' field for each project, then making a thicker bar for a higher number. How does it solve the user problems? I currently use colour coding to do something similar, but the colours are a little arbitrary, so it's not hugely intuitive. I could potentially also use the 'grouped by' feature to put bigger projects higher up and smaller lower down, but that's also not hugely visually immediate. I imagine this feature would also be useful to other users who wanted to get a similarly at-a-glance idea of the 'size' of a given record, or some other numerical quality. How was this validated? Not 100% sure what you mean here, but I've looked around and don't believe this is a feature or a currently suggested feature, but apologies if it actually is. Who is the target audience? Project managers, anyone else wishing to get an at-a-glance idea of the size of some aspect of a record when looking at it in timeline view.
... View more
Status:
New Ideas
Submitted on
‎Nov 28, 2024
11:51 AM
Submitted by
Lclore
on
‎Nov 28, 2024
11:51 AM
What is the proposed idea/solution? ...new element to inject code block into an interface. How does is solve the user problems? ...I could embed Airtable forms, embed Gmail, embed a VoIP phone into our APP so we don’t need to leave Airtable to execute those functions. How was this validated? ... Who is the target audience? ...basically everyone. This would make Airtable truly a complete app builder.
... 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 27, 2024
01:53 PM
Submitted by
smullin
on
‎Nov 27, 2024
01:53 PM
Hi, I'm super excited about the new date dependency features. I've manually implemented that before with automations. However, limiting the precision to "days" seems arbitrary and limits the functionality to project management. Increasing the precision to minutes or seconds (or whatever the standard is for dates) would vastly improve utility for things like batch scheduling. Cheers, Scott
... View more
Status:
New Ideas
Submitted on
‎Nov 27, 2024
07:27 AM
Submitted by
Jesse2
on
‎Nov 27, 2024
07:27 AM
Idea: Enable copy or export of pivot-tables in interfaces. This functionality already exists in the pivot-table extention in the data tab. But not in the interface tab. User problem: I need to use the data from the pivot table in another tool. Copying or exporting is not possible. Printing to PDF has its own issues. Validation: Scoured all over the internet for a fix and actually got nothing that would work. How does it solve it: It solves the user problem because its the easiest solution. Just allow me to copy my outcomes. Target audience: anyone that uses airtable but needs added functionality outside airtable. Enable copy or export pivot-tables in interfaces Extra information: Hi Guys, am working on a project were I use Airtable as database. I have an payd account. For cummunicating the outcomes of the project I use Flourish. The reason for this is because I need quite complex functionality for the graphs. Which airtable doesnt have and doesnt need to have. However, I cannot copy the Pivot table outcomes in the interface while keeping the table structure intact. Also, if i want to print the table to PDF and use OCR or Excel to extract the data to a structured table. I cannot always print the entire table, because the print-tool from airtable interface does not seem to understand that a pivot table can be bigger than 1 A4. The consequence is that it prints only partly, there is no option to scale. This functionality does exist in the pivot table extention in the data-section. However, the pivot table in the data tab misses some basic functionalities like aggregating.
... View more
Status:
New Ideas
Submitted on
‎Nov 26, 2024
10:56 PM
Submitted by
Ricardo_da_Cost
on
‎Nov 26, 2024
10:56 PM
What is the proposed idea/solution? There are two actions: Create and Update. Add a third option: Delete. How does is solve the user problems? When my client enters a follow-up date and the event_id doesn't exist, an outlook calendar event is created. Changing the date, updates the calendar event. Now the kicker, surely clearing the date field should delete the calendar event. It's natural to remove calendar entries. I know Make.com has the module but that means having to open an account, building the scenario, etc, etc. How was this validated? It's not there 🙂 Who is the target audience? Anyone using the Outlook Calendar actions.
... View more
Status:
New Ideas
Submitted on
‎Nov 26, 2024
01:42 AM
Submitted by
Craig_Toohey
on
‎Nov 26, 2024
01:42 AM
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
Status:
New Ideas
Submitted on
‎Nov 25, 2024
03:02 PM
Submitted by
china_kenyakeys
on
‎Nov 25, 2024
03:02 PM
What is the proposed idea/solution? The idea is to have a field that contains a custom number of check boxes that can be individually labeled. For instance 4 boxes labeled Y1 (for Year 1), Y2, Y3 & Y4 to track the number of years a sponsor has paid a student's tuition. I can see other uses as well. If you sell punch cards - buy 10 get the 11th cup of coffee or yoga class etc free. You could check off the number of times the punch card has been used. How does is solve the user problems? This solves this user from having to have multiple check box columns - it's cleaner. Automations could be created when all boxes are checked. I'm sure others smarter than me can think of many more uses. Please enjoy the very sophisticated drawing attached.
... View more
Status:
New Ideas
Submitted on
‎Nov 25, 2024
09:23 AM
Submitted by
DisraeliGears01
on
‎Nov 25, 2024
09:23 AM
What is the proposed idea/solution? I propose adding a reminder functionality into commenting that integrates with Airtable's Notifications function. Exact implementation could vary, but the ability to tag a user (or yourself) and select a length of time or an exact date when you'll receive an Airtable notification directing you back to the record. How does is solve the user problems? While date/time fields, calculations, and email automations can be utilized to create reminders for users in a record's data, that then becomes an integral part of a records data. Often I see a temporary change need to be enacted and returned to a month or two later, and being able to simply comment a reminder to re-visit the record would be invaluable. Instead of setting multiple fields and automations, integrating with the comments section provides a side space to set a "Hey! Come back to this!" reminder which fits the use cases of comments. Who is the target audience? All users, but particularly those managing ongoing data sets rather than discrete projects. In my particular case, we re-check our data records every 6 months, but occasionally there are scheduled changes (a location we document is closed until X date) which need to be expressed and then re-evaluated off schedule.
... View more