What is the proposed idea/solution? The Duration field now supports days in addition to hours and minutes. However, the formatting options for the Formula field, when the output is formatted as a date, do not accommodate this change. As a result, I cannot use DATETIME_DIFF() to calculate a duration of many days without resorting to the same steps required before the Duration field supported days. How does it solve the user problems? By allowing the Duration field to support days, users can more easily track and calculate longer periods of time directly within the field. This streamlines the process and reduces the need for complex workarounds previously necessary to handle durations extending beyond hours and minutes. How was this validated? The issue was identified and validated during the development and testing of an interface. Testing scenarios where users attempted to calculate durations of many days highlighted the lack of appropriate formatting in the Formula field as a significant pain point. Who is the target audience? The target audience includes users who need to track and calculate extended periods, such as project managers, event planners, and anyone involved in long-term scheduling or time tracking. These users will benefit from more straightforward duration calculations and improved usability of the Duration field. ... View more

When you add a Checkbox field to a table, you can choose a style graphic used when the box is checked. You can choose from many graphics like a Check, an X, a Star, a Heart, etc. When you add a Function field to a table that returns numbers, you have the option to format the numbers. However, If the function returns a Boolean, the field will display a 1 or 0.  (I know you can add code to the function to display graphics, but that shouldn’t be necessary.) It would be nice to see a checkbox-style format for Boolean values returned from Function fields. Having the option would make the UI consistent when displaying Boolean values and performing calculations on these fields. ... View more

What is the proposed idea/solution? My suggestion is that you make all desktop data views and interfaces phone fields function just like the mobile app so that if you click on it you have the option to choose Call or Text (tel/sms). Workaround is to at least make this work with the Button field, right now the tel: or sms: links do not work with the button in the data views or interfaces, they are just kind greyed out and don't work.  How does is solve the user problems? Most business run on computers not mobile phones. The option to just click a phone # and then choose call or text is an invaluable time saving option. Why do you have a phone number field that does not act like a phone number on a desktop from a data view or interface when it works like this in the airtable mobile app?! Is not one of the most common uses of airtable include CRM /customer data? How can I have a customer contact crm type database/interface that does not have native clickable phone numbers on a desktop PC when the mobile app has it built in? All webpages do this now, all CRMs do this now.  How was this validated? There isn't even a good work around for this!  adding a button with a URL tel: type link does not even work. Who is the target audience? Everyone who uses artable to manage cutomers... ... View more

When building a filter for the sake of linking a row to another row in the same table, it would be helpful to eliminate the accidental selection of the same row. For example, we are trying to match buy and sell transactions to each other inside the same table. We we build the filter to limit which rows are shown in the selector list, we filter on things like "SKU = This SKU" via dynamic data to pull in the current record's SKU. However, often the selection criteria causes the record we are editing to show in the quick select list, leading to easy mistakes. We'd like to add a filter to say something like "RecordID != This RecordID" but the recordID is an internal/API field only it seems.  I suspect I could assign an autoID field, but those are dynamic and we see a warning about dynamic fields not matching correctly when trying that.  To be able to do it on the recordID without a synthetic extra step would be an improvement anyway.   ... View more

What is the proposed idea/solution? An extra Action for the Button Field inside a table (not in the interface), where we can select "Run an Automation" How does is solve the user problems? At the moment there is no direct way to run a simple automation from a button field. it only works on buttons in interfaces. How was this validated? The press of the button should also "pass" the record ID to the automation, so any automation ran can use the record ID to specifically work on a record. Who is the target audience? This is useful for everybody who wants to use the button field in day to day simple operations.  ... View more

hey, Linked fields populated by formula !!!!!! I think it's so obvious and self-explanatory for everyone that has ever dealt with relational databases. this is a feature needed for yesterday, it just makes no sense we need to use all those workarounds and automations to get there, and although product is already so advance this is still not available :(( ... View more

I am trying to create a company budget database where all the accounts are in the main table (grid view), but some of them are subaccounts of other accounts (and others are sub-sub-accounts, etc.). All the parent/child relationships are between records in the same table. How do I display the data where the sub accounts are indented under their parent records and can roll up at each step of the hierarchy, if desired (including a calculated sum field) For example,  100 Personnel Costs ($250K) <-- This is a calculated roll-up from subaccounts         110 Salary & Wages ($200K)         120 Healthcare ($50K) 200 Facilities ($65K)  <-- Calculated         210 Rent ($30K)         220 Maintenance ($20K)         230 Exterior ($15K)  <-- Calculated                 231 Grounds ($10K)                 232 Signage ($5K) etc.... It would be nice to roll up the budgeted amounts for each subaccount into a field in its parent account. I tried the List view type, but that requires a relationship between records in two different tables.     ... View more

Converting a Single Select text string to a numerical value requires multiple fields and formulas.  This idea proposes a way to automatically convert a Single Select text string into a numerical value within a single Field. An additional build on this concept would be to include a formula calculation option within the single select field options.  See concepts below... User selects Text (e.g., "Minor Issues") and Airtable sees a numerical Value (in example below, "3")     Option B: Embed a Formula option within the field: User selects text string  "Jan" and Airtable sees 01/01/2024. (I realize example below is not correct formula) ... Currently this process requires 2-3 fields and formulas to convert a text string to a numerical value which clutter up the base very quickly. Also if the single select text string is long or if the choices change, creating and updating the formulas to convert to a value becomes extremely tedious.  .. No validation done yet ... Creators who are using text strings to make choices user friendly and they don't want to have multiple fields and formulas complicating the base.  ... ... View more

What is the proposed idea/solution? Creating a dedicated workspace for formulas that are on the bottom of the window in a Base that will generate greater visibility for formula expression writing.  It would also be very helpful if the formulas would have more predictive capabilities.   How does is solve the user problems? The current floating model is often too condensed to navigate or edit when dealing with lengthy formulas.  This would allow for greater visibility.  How was this validated? There can be a "expanding" button that could create either a pop up window or a lower page window for viewing the formula. ... Who is the target audience? ... ... View more