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

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

I have a table with many, many fields (150+).  Not all of these fields need to be populated.  In fact, most of them are sparsely populated based on conditions present in other fields. It would be awesome if in GRID VIEW there were a way to selectively "gray out" field values based on a formula (unique formulas per field would be ideal).  That way, users could visually know when to "skip" a certain field and focus their attention on others. I need this functionality specifically in GRID VIEW, because my users do a lot of visual comparisons between ADJACENT records -- and there's no easy way to do this visual comparison in any other view types currently. ... View more

What is the proposed idea/solution? I want to be able to add a color based on a formula. For example I have a bunch of subtasks under a parent task. I want to color the records where due date is greater than the parent task end date because this is a task I need to be flagged since the whole task should be done before it is currently planned. Ideally the formula would be,  IF({parent task end date} - {due date} < 0) and then I can set the color to yellow. ... View more

What is the proposed idea/solution? ...when changing the name of a Field in a Synced Table, the updated name should also be Synced. This would likely require a feature, whereby a Synced Field and a local Field can have the same name without a conflict. This should not be a problem, because it's easy to determine what is synced field vs local due to the lightning bolt icon. How does is solve the user problems? ...without this feature, any changes to a Field Name are not propagated to other Synced Tables. This causes confusion. How was this validated? ...Try changing the field name of a Synced Table and find out! It's frustrating. Who is the target audience? ...all users who use Synced Tables. ... View more

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

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

"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