Showing ideas with status New Ideas.
Show all ideas
Status:
New Ideas
Submitted on
‎Nov 28, 2023
08:37 AM
Submitted by
g4knr99
on
‎Nov 28, 2023
08:37 AM
The current grid view summarisation options are great, but we need the summaries to calculate the combined values when using formula fields. E.g. Each record calculates a % using two number fields. The summarisation doesn't give the total combined % but rather a sum, average, or another inappropriate function.
... View more
Status:
New Ideas
Submitted on
‎Nov 22, 2023
09:25 AM
Submitted by
g4knr99
on
‎Nov 22, 2023
09:25 AM
Capacity Rather than having time against items spread evenly over X days, having another junction table that tracks time entries would be great. For example, I have a 10-hour task to do over 3 days and spend from 10am to 4pm working on it on the first day. This leaves 4 hours of work to do, which can then be spread over the next two days. Should I then do none of that work on day 2, all 4 hours of it would need to be done on the 3rd day. Available hours The available hours are powerful, but don't allow us to track half days or exclude certain types of time off, both of which are crucial to utilisation. Many people take half days but these would appear in the timeline view as either normal days or time off, leaving the user in a position where they have to know when people are off work. It'd be ideal to select a view in the "Time off" table to filter out people who are off sick, at a conference or have had their leave request rejected, for example.
... View more
Status:
New Ideas
Submitted on
‎Nov 15, 2023
02:04 AM
Submitted by
Ander
on
‎Nov 15, 2023
02:04 AM
"When I use the selection field to group the list, and I want to change various records to a newly created group/selection, I have to go into each record and change each selection/group."
... View more
Status:
New Ideas
Submitted on
‎Nov 14, 2023
09:24 AM
Submitted by
Blake_Caldwell
on
‎Nov 14, 2023
09:24 AM
What is the proposed idea/solution? Simply have a setting for a field in the same table to automatically update its contents based on the values in another field. This would be like you did a copy and paste of the other field column into it. It's simply type conversion with both types persisting. You'll probably have to make that field non-editable, like a synced field or else allow for 2 way syncing if you want to get elegant. How does is solve the user problems? So many of our automations are put towards the simple task of updating data in one field with that of another. Managing this slows us down and limits our use cases (especially with automation limits). Examples: (1) This is especially important when making use of interfaces that limit the field types it can take advantage of for certain purposes. (2) Converting Formula fields into single/multi selects or linked fields. (3) Converting synced linked fields into a more usable format (a select or linked field) (4) Converting discreet form data into other types. Example, NPS forms require discreet numeric 0-10 answers that require a select, but the results are not numeric and must be converted to be usable for us. (4) There are tons of other use cases. Having to convert data types is ubiquitous across the platform. How was this validated? N/A Who is the target audience? Everyone Labels? I only chose fields because that is the core functionality we are discussing, but this will impact a variety of different parts of Airtable, including: Sync, Interface Designer, Base Design, Automations and Scripting, Formulas and Calculated Fields, Views and forms, and even improve ease of use for some extensions.
... View more
Status:
New Ideas
Submitted on
‎Nov 13, 2023
05:45 AM
Submitted by
bweber
on
‎Nov 13, 2023
05:45 AM
Can we add two new "bucket by" options on interface charts? I would like to view my data by the half hour and by the quarter hour to see when people are checking out of our space.
... View more
Status:
New Ideas
Submitted on
‎Nov 13, 2023
03:57 AM
Submitted by
arandomstring
on
‎Nov 13, 2023
03:57 AM
Please extend the comments feature so that it is broader than the limited focus of per record comments. Enhanced Collaborative Communication: By allowing comments at different levels, team members can have more context-specific discussions. This feature would enable users to leave comments on a specific base, table, or view, fostering clearer, more organized communication. It would essentially turn Airtable into a more collaborative workspace, where team members can easily discuss broader strategies at the base level, specific data sets at the table level, and particular views or filters. Improved Workflow Management: This feature would be a game changer for project management. Teams could streamline their workflow by discussing and tracking changes directly within Airtable, reducing the need for external communication tools. This centralized communication would lead to fewer misunderstandings and a more cohesive workflow, especially in remote or hybrid work environments. User-Friendly Experience: Embedding comments at different levels would make Airtable more intuitive and user-friendly. Users could easily navigate to relevant discussions without having to sift through unrelated comments at the record level. This is particularly beneficial for new team members who need to quickly understand the context and history of a project. Comments at the view level strike me as being the most useful - views are where most work is taking place and being able to have focused discussions at that level next to the data would be incredibly useful.
... View more
Status:
New Ideas
Submitted on
‎Nov 09, 2023
11:58 PM
Submitted by
JamesS
on
‎Nov 09, 2023
11:58 PM
I have a database of members of an organisation and I from time to time I do an information check where I email them (using SendGrid) and ask them to confirm the information or reply with any edits. In its current format they have to reply to the email with any changes, or just to confirm. My request would be to be able to include buttons in the outgoing email that they can use to confirm. The button they click will then populate a Single Select style field in the original table. If they select 'No' however then they would have an option to list any corrections that would then populate in a Long Text style field in the original table. I would then be able to Group using that particular field so I would always be able to see who has and who has not replied.
... View more
Status:
New Ideas
Submitted on
‎Nov 08, 2023
09:04 AM
Submitted by
shanahanmp
on
‎Nov 08, 2023
09:04 AM
The issue is that in interfaces, the search feature hides rows of data that do not contain the keyword you are searching for in a grid view. This limits your ability to search and compare all rows of data. This feature is possible when you use the search function in a data table but not in an interface.
... View more
Status:
New Ideas
Submitted on
‎Nov 06, 2023
09:24 AM
Submitted by
BScholnick
on
‎Nov 06, 2023
09:24 AM
What is the proposed idea/solution? Feedback from a UX perspective: It would be really helpful if there was a menu item on each base that takes the user to the base’s workspace. How does is solve the user problems? It would save me time from going back home and scrolling through all of my workspaces to get to another base within the same workspace How was this validated? Experience; it would help all users ...
... View more
Status:
New Ideas
Submitted on
‎Oct 31, 2023
05:44 PM
Submitted by
royalassistants
on
‎Oct 31, 2023
05:44 PM
What is the proposed idea/solution? This will help me to create a full duplicate of a table to another based with or without the data... How does is solve the user problems? Having to copy and pause the table details and have to relabel form questions ... ...
... View more