Showing ideas with label views and forms.
Show all ideas
Status:
New Ideas
Submitted on
‎Oct 02, 2024
12:01 AM
Submitted by
Cameron_Rout
on
‎Oct 02, 2024
12:01 AM

In my experience, tags are things that are added by the user, not by the admin. While tagging photos for example, it's almost impossible to predict what tags will be used. Make it so that I can add items in the multiselect interface. This could be an option in the field definition "Allow users to add options". This would work well with the other feature request I saw on here about showing how many of the other tags there are.
... View more
Status:
New Ideas
Submitted on
‎Sep 26, 2024
05:46 PM
Submitted by
airballer86
on
‎Sep 26, 2024
05:46 PM

I would like to copy filters from multiple views and combine them in one single view. I'm getting to the point where one view has what I need and I want to compare it with another view. The current solution is to hire an engineer to write a script or painstakingly rebuild one filter onto an existing one. I've seen this idea before and will hope a new 'request' will resurface the need for more reusable functionality around filters.
... View more
Status:
New Ideas
Submitted on
‎Sep 26, 2024
01:39 PM
Submitted by
JeffJohnVol
on
‎Sep 26, 2024
01:39 PM

On filter options, it would be useful if there was an option on the comparitor to be "in list" and "not in list". After either of these are selected, you can reference another record/view and a field to represent that list. As an example, lets say there is a table of "Teachers" and some of them have a "Teacher Type" field of "Art","History","Math", etc. A view might be created to have a list of just Art Teachers ("Teacher Type" is "Art"). It would be nice if on another table that references Teachers that are interested in art projects, there could be a condition that says "Teacher" "is in list" Table:Teachers; View "Art Teachers". And yes, I realize that this can probably be done by a mixture of linked tables and adding additional conditions within the view, but this methodology allows people to break down their views into simpler organizational blocks to be used in different places. If I have a need to get Art Teachers in 10 other views, I don't want to have to add all the extra table links and conditions for all 10, if I can just do the "in list" and leave the Art Teacher designation in one view. Hopefully this makes sense. Thanks.
... View more
Status:
New Ideas
Submitted on
‎Sep 26, 2024
01:21 PM
Submitted by
JeffJohnVol
on
‎Sep 26, 2024
01:21 PM

What is the proposed idea/solution? When creating a grid, you have filter and sort. Add "limit rows returned". How does is solve the user problems? Lets say you have scheduled meetings, and you want to have a view that just lists the next meeting. You can filter to have scheduled date "after today", and sort it automatically so the next meeting is at the top. But there's no way to limit to the top row. If you had a row limit with the options of ("Show All" (default), "First Row Only", or "Specific Limit" (with value), I can see this type of view being very handy when driving some automations. It would also be incredibly handy for people that want to schedule a price increase. Lets say I have 4 dates with 4 different prices, it would be possible to list the most current price by using a mixture of the max date that less than current, and showing the top row. How was this validated? Pretty basic. If you say only show 3 rows, only 3 rows should show up on the view. Who is the target audience? Anyone that has complex data sets that are driven by schedule, or any other data set where they want to limit results based on a filter/sort such as "top 3 winners".
... View more
Status:
New Ideas
Submitted on
‎Sep 04, 2024
04:44 PM
Submitted by
thelus
on
‎Sep 04, 2024
04:44 PM

What is the proposed idea/solution? In the Timeline view, I'd love to see a slightly more granular hourly view than "Day split into hours." Most of the records in my base are no more than an hour long, and there tend to be a few phases of the day where they bunch up a lot, which makes the "Day split into hours" zoom level really difficult to read. If there were something more zoomed in, even something as simple as "12 hours split into hours," that would help a lot. (The ability to freely zoom would be even better, but that might be too much to hope for!) When it comes to looking at shorter-duration events at a glance, the calendar view is easier to read, but Grouping is where the Timeline shines, and exactly what I need it for.
... View more
Status:
New Ideas
Submitted on
‎Aug 29, 2024
03:14 PM
Submitted by
PedroCerrano
on
‎Aug 29, 2024
03:14 PM

What is the proposed idea/solution? Add the ability to insert a Condition (like in Rules > Visibility) on the Submit button of a form. Possibly even run an automation to check values in other tables before Submitting a form. How does is solve the user problems? A dynamic Form Limiter prevents unwanted Submissions that a Collaborator won't have to clean up later. Who is the target audience? Airtable is a significant step up from Survey Monkey, but there, I'm able to limit the number of form submissions.
... View more
Status:
New Ideas
Submitted on
‎Aug 23, 2024
01:07 PM
Submitted by
Shabushi11
on
‎Aug 23, 2024
01:07 PM

I love the new forms interface, and I am glad it finally made it in the navigation bar. Now if you could please allow for forms in that view to be segmented into sections that would be amazing. Currently only allows to add new forms to the list, but there is no add section in the Form View column.
... View more
Status:
New Ideas
Submitted on
‎Aug 22, 2024
08:21 AM
Submitted by
Alyssa_Hitchcoc
on
‎Aug 22, 2024
08:21 AM

What is the proposed idea/solution? In interface page layouts, add the ability to collapse groups so that the header is visible but the fields nested beneath are not. An added bonus would be the ability to select whether a group is expanded or collapsed by default in the page template.... How does is solve the user problems? I have several interface page views that are quite long, and not all groups are applicable to all records. Allowing me to collapse the groups that are not relevant would make it easier for me to see and edit the most important information efficiently. How was this validated? This is generally accepted as useful functionality and exists in other places in the Airtable app. Google docs just recently added this functionality as well. Who is the target audience? Anyone using interface page views with many forms/groups
... View more
Status:
New Ideas
Submitted on
‎Aug 15, 2024
11:02 PM
Submitted by
James3
on
‎Aug 15, 2024
11:02 PM

What is the proposed idea/solution? For our projects we schedule around a keystone/constraint/foundation task. It would be nice to be able see where this keystone task sits when the items in group are collapsed. This way, we can drag the whole group backwards and forwards without having to expand the view and select all the tasks, which is slow. In view settings, would be able to optionally specify "Keystone task name" which would be highlighted in collapsed view, and also when expanded. Example: How does it solve user problems? Increase speed and effectiveness of adjusting projects with a focus on a key resource. How was this validated? Can't validate UI elements, but can confirm that rescheduling a collapsed group is much easier and quicker. Only trouble is need to expand to be able to see constraint resource! Who is the target audience? Anyone using Airtable for project management
... View more
Status:
New Ideas
Submitted on
‎Aug 14, 2024
07:46 AM
Submitted by
Saravanan_009
on
‎Aug 14, 2024
07:46 AM

What is the proposed idea/solution? The proposed solution is to introduce a feature in Airtable's Kanban view that allows users to manually reorder columns when using linked fields, just as they can with single-select fields. This would involve a drag-and-drop functionality where users can click and move columns into their preferred order, rather than having them automatically sorted alphabetically. How does is solve the user problems? Currently, users are limited by the automatic sorting of columns when using linked fields in Kanban view, which can lead to a less intuitive workflow and makes it harder to organize tasks effectively. By allowing manual reordering of columns, users gain the flexibility to arrange their Kanban boards in a way that best fits their workflow and priorities. This would improve the usability of Kanban views, particularly for teams working on complex projects that require customized task organization. How was this validated? The need for this feature has been highlighted by user feedback and the limitations experienced by teams who frequently use linked records in their Kanban views. The idea builds on existing functionality (manual reordering for single-select fields), so it’s a natural extension of a proven feature. While there may not be formal studies validating this specific solution, it is grounded in practical user experience and the need for greater customization in Airtable. Feedback from the Airtable community, including forums and support channels, often reflects a desire for more control over how data is displayed and managed, validating the importance of such a feature. Who is the target audience? The target audience includes Airtable users who rely on Kanban views for project management and task tracking, especially those using linked fields extensively. This feature would benefit teams and individuals looking for more control and customization in their project management processes. It is particularly relevant for users managing complex projects with multiple linked records where the ability to organize columns manually would improve workflow and visibility.
... View more