What is the proposed idea/solution? Let us create custom terms for records in tables in addition to selecting from the predefined list.  How does is solve the user problems? The list provides a great starting point for record names, but too often terms aren't available. For instance, Phone Number isn't an available term, despite having a record field type of Phone Number, and neither is Number. This translates to the interfaces any time an 'Add Record' button appears to a linked record field, which may cause confusion if an intuitive term is not available. This is a relatively small ask (that I do not understand the technical requirements of at all, so please don't misunderstand me) that would go a long way to improve the user experience, especially to those users less tech-savvy than others. How was this validated? Every single time I've searched for a term in the pre-defined list of terms for records, I almost always come up empty. Who is the target audience? Moreso end users unfamiliar with Airtable who see a button to add/create/link records.  ... View more

What is the proposed idea/solution? I would like to be able to colorize the full Row. I would like to set different color for the full row instead just a colorized label at the beginning of the row.       ... Who is the target audience? ... ... View more

To whom it may concern, An enhancement suggestion from Kalypso: Update the Date Dependencies configuration such that it assumes that when Start and Due Dates have been established and a Predecessor is changed, the Start and Due dates are updated instead of assuming those dates should stay the same and adjusting the Buffer. Alternatively, this could be a toggled option if current behavior is desired for some organizations.  Expected Benefits: Enable the ability to set the Date Dependency behavior to align to an organizations use case. For those that would desire assuming dates should be updated, it will make it more efficient to updated without having to navigate between two separate views to make the update.  Please consider adding this capability.  Regards, Jason Knighten ... View more

To whom it may concern, An enhancement suggestion from Kalypso: While it is currently possible to link multiple Predecessors, the date calculations do not consider the impacts of any Predecessors beyond the first one. This can get complex but here is a pass at recommending how the solution should be designed: Finish to Start dependent task should base it's start date on the maximum finish date of all dependent tasks Example: Task 3 is dependent on Task 1 and Task 2. Task 1 ends on 10/24 and Task 2 ends on 10/31. Since Task 3 is Finish to Start and dependent on both tasks being completed, it should use the Task 2 10/31 finish date to define the Task 3 start date as 11/01. Start to Start dependent task should base it's start date on the maximum start date of all dependent tasks Example: Task 3 is dependent on Task 1 and Task 2. Task 1 starts on 10/19 and Task 2 starts on 10/26. Since Task 3 is Start to Start and dependent on both tasks having started, it should use the 10/26 start date to define the Task 3 start date as 10/26. Finish to Finish dependent task should base it's finish date on the maximum finish date of all dependent tasks Example: Task 3 is dependent on Task 1 and Task 2. Task 1 ends on 10/24 and Task 2 ends on 10/31. Since Task 3 is Finish to Finish and dependent on both tasks being finished, it should use the 10/31 finish date to define the Task 3 Finish date as 10/31. The start date would then be calculated based on the Duration of Tasks 3. Start to Finish dependent task should base it's finish date on the maximum start date of all dependent tasks Example: Task 3 is dependent on Task 1 and Task 2. Task 1 starts on 10/19 and Task 2 starts on 10/26. Since Task 3 is Start to Finish and dependent on both tasks having started, it should use the 10/26 start date to define the Task 3 Finish date as 10/26. The start date would then be calculated based on the Duration of Tasks 3. Expected Benefits: Improve ability to build dependencies to match real world dependencies requirements Please consider adding this capability.  Regards, Jason Knighten ... View more

To whom it may concern, An enhancement suggestion from Kalypso: Type and Buffer, currently only available to update in Timeline view, should be part of the Date Dependencies required fields and thus available for update in other views and/or with Automations.   Expected Benefits:  Ability to configure all elements of date dependencies in any view Enable ability to use Type and Buffer fields as Automation triggers or targets of automation updates Please consider adding this capability.  Regards, Jason Knighten ... View more

To whom it may concern, An enhancement suggestion from Kalypso: When using the Date Dependencies settings, Start dates (And due dates if a Duration is already set), should auto populate when a Predecessor is selected.  Currently, dates are not initially set by selecting the Predecessor and invalid dependency error is displayed which is not fixed by opening and selecting Fix all However, the dates are updated if, after setting the Predecessor, the date of the Predecessor is modified or the Due or Start dates as manually set Screen shot after having entered a Duration and selecting Predecessor.  Selecting View All for the 1 Invalid Dependency error and selecting Fix All has no effect. However, if I update the date in the Predecessor, or select a date in the dependent task, then the dates are displayed.  Here I changed the date in the Predecessor and the dates in the dependent task populate.  Here, (after undo), I have selected the start date of the dependent task.  Neither of those solutions should be necessary. Expected Benefits: More efficient and less confusing data configuration process for project schedules that utilize Date Dependency features. Please consider adding this capability.  Regards, Jason Knighten ... View more

What is the proposed idea/solution? Add "Prompt" as an answer to "What should each record be called?" How does is solve the user problems? How was this validated? See images above. I wanna use my table as a prompt library Who is the target audience? Er'rybody ... View more

What is the proposed idea/solution? Airtable base needs a special table (or method) for adding and managing data related to collaborators. I mean this by team members. How does is solve the user problems? Think that you're tracking work hours of your team and everyone can go and add their own hours via interface or something else. Now you should be able to add "global" data related to who has done the record (or marked as collaborator to that data). For example hourly salary, work hours etc. Sky is the limit really. It would replace the "normal" way employees/users are "meant" to be done now. Being able to link that data to collaborator in base level would solve many issues with data linking and keeping them organized. Also it then should be possible to lookup and rollup data based on linked collaborator(s). So basically the "collaborator" field would be just a special kind of link to another record and every base would have this one special table just for them. Or something similar. Who is the target audience? Everybody who use collaborator field. ... View more

Context: our Airtable account hits the automation run limit every month.  I believe we've upgraded to the plan with the maximum allowable amount of automation runs.  FWIW: I would pay more for more automation runs, and would pay a lot for unlimited automation runs. Situation: There is a limit/cap on automations that can be run, per month There are a number of different automations based on a variety of triggers, across tables and bases Idea would address these two issues: Cannot currently maintain and/or optimize for a functional account, that will remain under the monthly automation limit, without access to the centralized automation run log Cannot currently troubleshoot or trace an issue when an automation is running, but it's not clear what is triggering it/in which table Thanks in advance for considering. ... View more