Showing ideas with label fields.
Show all ideas
Status:
New Ideas
Submitted on
Feb 21, 2025
08:01 AM
Submitted by
eduardo
on
Feb 21, 2025
08:01 AM

What is the proposed idea/solution? Add formatting options for user fields. Specifically, provide the option to display first names only (e.g., Eduardo). Additional options, such as displaying first names with initials (Eduardo M.) or profile pictures only (which default to initials for users with no set profile picture) would also be helpful, if possible. How does it solve the user problems? Adding these new formatting options would help make large grids more compact by shortening the column width of user fields, resulting in a more efficient use of screen space. Small teams might also appreciate the option to display first names only if they are looking to strike a more casual tone. How was this validated? N/A Who is the target audience? Anyone who uses user fields in their Airtable bases.
... View more
Status:
New Ideas
Submitted on
Feb 19, 2025
07:09 AM
Submitted by
OlhaZalevska
on
Feb 19, 2025
07:09 AM

Hello! It would be great to have the option to hide Prefill Fields in a form, especially when pre-filling fields with dynamic data. In my case, I have a table with users, and I need to add more information about them. To do this, I create a new table and a form. Then, I set up an automation to transfer some data from the new form to the main table. I will repeat this process several times, as I need to conduct multiple surveys at specific time intervals. The problem is that I need a reliable unique identifier. I would like to send each user an individual URL with Prefill Fields containing their unique ID. However, I don’t want them to see or modify this ID. Unfortunately, I don’t see an option to create a truly hidden field in standard forms—only conditional fields. Thanks for considering this request!
... View more
Status:
New Ideas
Submitted on
Jan 20, 2025
05:49 AM
Submitted by
FormsUser
on
Jan 20, 2025
05:49 AM

I often develop Airtable forms for use in youth afterschool programming. Since many of our participants are minors, it is important that we document their ages. In Airtable forms, I add the date field for prospective participants to enter their DOB and make it a required field. I set the "Range Minimum" to the latest date someone could be born and qualify for program (so, if a program requires you be 18 to participate, the "Range Minimum" to the latest date someone could be born and still be 18 by the program start date). Problem is, you have to click through each of the months of each year to get to the far past. This is time-consuming, and having the ability to type in a date would really save time. Overall, the Airtable team should look into allowing the date field to be used for more than just tracking dates connected to things other than just project timelines. Who is the target audience? People who use forms and other Airtable features to track age or other dates that occurred in the far past. This is NOT for people tracking future deadlines or team project timelines, as it seems that the Date field is currently configured with those users in mind.
... View more
Status:
New Ideas
Submitted on
Jan 12, 2025
06:51 AM
Submitted by
Frite666
on
Jan 12, 2025
06:51 AM

Sems stupid to say the least but it is impossible to diplay most currency and units correctly because the Currency field dosen't allow the "currency symbol" to be displayed after the value. Adding a radio/checkbox to choise between the 2 options would be great. It could be added right here There is a post by @.Theo_Zachmann about it posted in 2017 (almost 8 years prior) and it has neither been anwsered by the Airtable Team or implemented yet.
... View more
Status:
New Ideas
Submitted on
Jan 12, 2025
04:12 AM
Submitted by
Frite666
on
Jan 12, 2025
04:12 AM

With Rating being a type, it should be possible to format look up and formula into a directly into Rating. Right now this is not possible, without the use of Automation even so a rating is a disguised Number. Adding this functionnaly would help application that have to deal with things like community ratings. Because a Rating is Number between 0 and a max rating, the resulting value in a formula should be clamp with 0 as the min and the max rating as the max.
... 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
Jan 02, 2025
08:13 AM
Submitted by
mattrpg
on
Jan 02, 2025
08:13 AM

What is the proposed idea/solution? When seeing a change in a field of a record in the activities feed it would be very helpful to be able to click on that and jump to the field. How does is solve the user problems? Because the information is truncated, being able to jump to a field with full data will make it easier to collect and make that information actionable. How was this validated? ... Who is the target audience? Anyone who wants to be able to more easily navigate through a record without scrolling through dozens and dozens of fields.
... View more
Status:
New Ideas
Submitted on
Dec 11, 2024
01:08 PM
Submitted by
Chais_Meyer
on
Dec 11, 2024
01:08 PM

Proposed Idea/Solution: The idea is to introduce a “Default Column Order Template” in Airtable. This template would allow users to define a consistent column order that automatically propagates to any views linked to the template. For example: •If View #1 and View #5 could both reference the same “Default Column Order Template” (e.g., “Template: Customer Service Data”), any changes made to the column order in the template would dynamically apply to both views, maintaining consistency. •While linked views would share the column order, they could still independently choose to show or hide specific fields/columns, giving users flexibility while ensuring a uniform structure. This feature would save time, enhance collaboration, and reduce errors caused by inconsistent column arrangements across multiple views. How Does It Solve User Problems? This feature addresses several challenges: 1.Efficiency in Multi-View Management: Users working with multiple views often need a consistent column order to streamline workflows. Manually maintaining the same column order across multiple views is time-consuming and prone to errors. A default column order template would ensure consistency across views with minimal effort. 2.Team Collaboration: In collaborative environments, different team members might use different views of the same data. Having a consistent column order ensures everyone is aligned, reducing confusion and making it easier to locate fields. 3.Improved User Experience: For projects involving multiple teams (e.g., customer service, marketing, and analytics), a unified column order reduces onboarding time for new team members and enhances data usability. 4.Dynamic Data Adjustments: As fields are added, removed, or reordered in the template, linked views dynamically reflect those changes. This ensures up-to-date and organized data without requiring manual updates in every individual view. How Was This Validated? While this request arises from a practical need observed in real-world workflows, its benefits have been implicitly validated through user behaviors and existing challenges: 1.User Feedback Patterns: Many Airtable users express frustrations in forums and support requests about the manual effort required to maintain consistent views. This feature would directly address such feedback. 2.Analogous Features in Other Platforms: Systems like spreadsheet templates or CMS tools often offer shared configurations for layout or structure. These serve as precedent for the efficiency and utility of such a feature. 3.Internal Testing Opportunities: Airtable could validate this feature through beta testing or user surveys, targeting teams or users managing complex bases with numerous views. Additional Use Cases: 1.Customer Relationship Management (CRM): A sales team and customer service team might use different views of the same customer data. Maintaining a consistent column order ensures smooth transitions between teams without data disorientation. If 50% of their views need to be different, for their CS team as an example, then that team would use their own template! 2.Project Management: A project manager might create views for “High-Level Overview” and “Detailed Task Tracking,” where consistency in column order aids in quickly understanding data context. 3.Event Planning: An event planning team could have separate views for “Guest List,” “Catering,” and “Budget,” but benefit from a unified column order to avoid confusion when cross-referencing data. 4.Analytics & Reporting: Analysts working with multiple dashboards can maintain uniform field arrangements, making it easier to compare and combine data. This feature would be a game-changer for users managing multiple views and collaborating across teams, ensuring Airtable continues to be a leader in dynamic data management.
... View more
Status:
New Ideas
Submitted on
Dec 09, 2024
01:52 AM
Submitted by
Paul_Thompson
on
Dec 09, 2024
01:52 AM

We need a 'Conditional Select' type field to add to forms. This type of single select and multi select question would conditionally disable and 'grey-out' specific options in select questions on forms. It doesn't seem currently possible to do this. There would be many use cases for this. My particular one is that I have a form for view only users to update certain fields in a database for a not for profit or charity music school recording students and musical instruments loaned to them. We need to prevent students resigning but not handing instruments back. The first single select question on the form is "What do you want to do?" which hides/shows various fields on the same form. One of the options is to resign a student. If that student is still holding an instrument, (ie. {instrument ID} is not blank) It should not be selectable, but should still be visible, greyed out so that the user can see they are in the right place and its clear they cannot select that option. An important feature of the proposed conditional select field would be the option to include a warning message when the disabled option is clicked or hovered over, which should allow the inclusion of variables from the source field causing the restriction. ie. in my use case, I would want to say, "{First name} cannot be resigned at this time because records show they are still holding the instrument {Instrument ID}. I think this feature would be of great benefit to a lot of Airtable users.
... 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