Boolean Filter Modifier

Bob_Clarke · ‎Dec 15, 2022

What is the proposed idea/solution? Currently the filters in Interface for a Boolean filter is limited to "is". The user does not have the option to "ignore the field" by leaving it unchecked . Unchecked pulls up all unchecked records, checked pulls up all checked records. This is too rigid of an option and causes user to get confused by the records they see when they don't check the box in the filter. When you press the "reset" link next to the filter, the user thinks they are seeing all the records when, in fact, they are seeing only the unchecked records. The solution would be to have 2 options for the modifier "is" and "any". The checkbox is grayed out or hidden if the user selects the "any" modifier.

Brent_Cook · ‎Dec 07, 2022

What is the proposed idea/solution? ...It would be very helpful to have kanban views be able to open to collapsed cards. I have two views that are great and useful, How does is solve the user problems? ...but collapsed cards would limit the amount of time searching for the desired one. How was this validated? ...by the time that it takes to search for the kanban, or time it would take to collapse all the cards Who is the target audience? ...everyone who has kanban views that contain large amounts

gaston · ‎Nov 01, 2024

What is the proposed idea/solution? While Copilot is great to kickoff a draft quickly, most of the times we would start builds from scratch. It would be great to have the AI generation option besides the "start from scratch" when creating a table. This would save sooo much time. In brief description the user can describe the fields to be included. How does is solve the user problems? Saves time when building tables How was this validated? ... Who is the target audience? Any Airtable Power User.

saknapp · ‎Oct 29, 2024

What is the proposed idea/solution? Only allow certain interface page groups to be visible to specific users How does is solve the user problems? Not everyone on large teams needs to see all the information How was this validated? Some fields are visible to all that do not need/want to be Who is the target audience? Enterprise users with multiple teams working in a base

MichaelSargent · ‎Oct 24, 2024

Currently, if you have multiple layouts of an open record panel that are used in a variety of places, when you go to delete a layout, it will only tell you where it's being used. That's all fine and well but then you have to go hunt down each individual place where that's being used which, depending on the size of your interface(s), can be nearly impossible which means you're removing the ability to click into records in those locations. There should be an option when deleting an open record panel layout to default all locations that are using **bleep** to change to another layout of your choice. This would tremendously help consolidating layouts. If Airtable really wanted to tackle this problem (which of course would be an Enterprise, possibly Business plan feature) would be a central place that manages all layouts for all datasets. But at the minimum, all Airtable users should have a 'default to another layout' option when deleting a layout.

Daniel_Selzer · ‎Oct 23, 2024

In interface designer using a standard view, I can turn off field labels, but when I'm in grid or gallery views, and click to enter a specific record, I can't turn off those same labels. They are redundant and add clutter and I'd love to be able to turn them off.

Ramosh · ‎Oct 22, 2024

In order to enforce standardised user management and permission policies on admin panel or through Enterprise API it would be great to be able to disable invite/share notifications. E.g. when changing from workspace permissions to equal base permissions users are notified. This causes users to get huge amount of email notifications and some might flag those as spam.

Jason_Knighten1 · ‎Oct 16, 2024

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

Jason_Knighten1 · ‎Oct 16, 2024

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

Jason_Knighten1 · ‎Oct 16, 2024

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

Boolean Filter Modifier

Kanban Collapsed Cards

Create new table with AI

Interface page groups visible to certain users

Option to default to existing Open Record Detail when deleting a layout

Turn off field labels in record view

Disable invite/share notifications

Predecessor change should adjust Start and Due dates instead of Buffer.

Type and Buffer fields should be standard fields for Date Dependencies Soltutions in all Views

Enable ability to calculate Date Dependencies when using multiple Predecessors

Format Formula as Checkbox

CSV Import in Interfaces

React to Record Comments

Allow Emoji reactions to comments

Multiplying by percent column yields result that i...