Showing ideas with label formulas and calculated fields.
Show all ideas
I'd love to be able to designate universal variables that could be referenced from any table in a base. So, for example, if I have a sales tax rate of 8%, I'd like to set that sales tax rate in one single place and then be able to reference that in formulas across the entire base. Currently, if I want to set up this type of variable, I need to 1) create a table of variables then 2) make sure every single record in the other tables is linked to the variables table 3) add a lookup field to every table that looks up this universal variable 4) create a formula which references this variable in the lookup field. For each universal variable, one should be able 1) give it a unique name that could be referenced in formulas across the entire table 2) set a data type (number, currency, percentage, etc) Then, if the sales tax rate changes, I just update the reference variable, and the changes propagate to all the formulas in the base that reference it. It's true that this could be done with manual copy paste or automations, but that's a LOT of work or automations for a very basic bit of functionality. It could easily eat into an automations cap on an AirTable plan. I imagine that it is pretty easy to script for someone who knows how to code, but that's a lot of work (or vendor cost) just to set a variable. I'd love to be able to tell AirTable: "I'm creating a universal variable called "SalesTax". It is a percentage variable." Then enter the number 8% and be done.
... View more
Status:
New Ideas
Submitted on
Jan 12, 2025
04:12 AM
Submitted by
Frite666
on
Jan 12, 2025
04:12 AM
![5 - Automation Enthusiast 5 - Automation Enthusiast](/html/@8E0586A35C6D0D07EA6A610CF7AEF6BF/rank_icons/Rank-AutomationEnthusiast.png)
With Rating being a type, it should be possible to format look up and formula into a directly into Rating. Right now this is not possible, without the use of Automation even so a rating is a disguised Number. Adding this functionnaly would help application that have to deal with things like community ratings. Because a Rating is Number between 0 and a max rating, the resulting value in a formula should be clamp with 0 as the min and the max rating as the max.
... View more
Status:
New Ideas
Submitted on
Oct 01, 2024
03:02 AM
Submitted by
SamGluck
on
Oct 01, 2024
03:02 AM
![6 - Interface Innovator 6 - Interface Innovator](/html/@781FA7B006C69ED0612A0090F8465157/rank_icons/Rank-InterfaceInnovator.png)
What is the proposed idea/solution? Currently we've got the option of formatting a formula field as a single select, I'd like to format it as a muliple choice How does is solve the user problems? I'd use this feature for labeling records with what fields still need to be filled. Lets say the Name and Email fields are empty, it would show at the top of the record red labels of what information still needs to be filled in the record, and as you enter the info, the labels disappear. Yes you can use automations with a script for this, but it doesn't work instant. it takes 10-15 seconds per run. using a formula would be instant.
... View more
Status:
New Ideas
Submitted on
Jul 30, 2024
07:21 PM
Submitted by
kuovonne
on
Jul 30, 2024
07:21 PM
![18 - Pluto 18 - Pluto](/html/@EB3D12BA2A0BCA205CD1572C5D621AAA/rank_icons/Rank-Pluto.png)
What is the proposed idea/solution? Formula fields have recently gained the ability to be formatted as single selects and checkboxes. I propose that formula fields also have the ability to be formatted as users and rich text. How does is solve the user problems? User fields are very useful for filtering records in interfaces, especially for filtering on the "current user". However, currently, the filter only works on actual user fields, but sometimes the user should be a calculated value. For example, a record might have a different assignee, depending on the stage of the record. It would be useful to have a formula field calculate the current assignee so that the interface page can then show all of the records where the user is a current assignee. For rich text fields, I currently have a formula field that serves as a template to build paragraphs in markdown, combined with an automation that copies the formula result to a rich text field. If the formula field could be formatted directly as rich text, I would not need the helper rich text field or the automation. This would also reduce issues with determining when the automation needs to be re-triggered. How was this validated? Based on my experience with Airtable, I think these features would be useful. Who is the target audience? ...
... View more
Submitted on
Sep 28, 2022
09:09 AM
Submitted by
Joel_Lee
on
Sep 28, 2022
09:09 AM
![6 - Interface Innovator 6 - Interface Innovator](/html/@781FA7B006C69ED0612A0090F8465157/rank_icons/Rank-InterfaceInnovator.png)
First, let me start off by saying how incredibly important this feature is. The data so many organizations could have by being able to create custom calculated metrics in Interfaces is untellable. When creating big numbers (like the Numbers widget in an Interface), you are tired to a specific field, then you must select an operator. For example, you tie that Number widget to a field in one of your tables, for example, “Revenue,” then select “Sum” and it gives you the total. Let’s say you did that same thing for “Profit.” Then, with those two metrics, there is no way to create a third one based off those that calculates, for example, something like: Profit / Revenue (displayed as a percentage (Margin)). The problem is that the only workaround to achieve the above (something that is a basic feature in, for example, Google Data Studio), is to build in the Profit, Revenue, and Margin fields at the table level which can fail to work if you are dealing with a metric for which there is no workable operator. For example, you cannot use “Sum” in the settings of a Number widget in an Interface in order to sum up all the “Margin” values in your table. That doesn’t make sense. Long story short, I would love if, in Interfaces, you could calculate your own metrics. The flexibility this would provide would help people who are using Interfaces for basic financial or other number-based widgets, and could give them the insights they need (like the organization I work for!).
... View more
Status:
New Ideas
Submitted on
Feb 14, 2024
11:00 AM
Submitted by
Ringthebells86
on
Feb 14, 2024
11:00 AM
![6 - Interface Innovator 6 - Interface Innovator](/html/@781FA7B006C69ED0612A0090F8465157/rank_icons/Rank-InterfaceInnovator.png)
Airtable finally added this calendar month as a date filter option which is great, however there needs to be a last calendar month instead of just last month. We need to submit every month our expenses from the previous month. So for example today, I need to be able to see all expenses from January (i.e. last calendar month). How it is now if I do last month, it will show me expenses from Jan 14 - Feb 14 which is not useful.
... View more
Status:
New Ideas
Submitted on
Sep 18, 2023
08:30 AM
Submitted by
Andy_Lin1
on
Sep 18, 2023
08:30 AM
![9 - Sun 9 - Sun](/html/@55B5758970FB924803A65D77A203713D/rank_icons/Rank-Sun.png)
I'd like to see a formula function for looking up values in linked records, something like: LOOKUP({Linked Record field}, {Field in linked table}) Basically, a two-criteria lookup similar to "INDEX MATCH MATCH" in Excel without needing to import all the fields from the linked table into the current one. Or just a dot/membership operator in SQL databases. Currently, if I want to fetch data from a linked record, I need to use a Lookup field. This is fine if I want to display the field's values in my table or consistently refer to it in a formula; but if I have multiple fields I want to reference in a single formula, then I would need to add a Lookup field for each of the source fields. This adds an number of extra fields to my base that only serve a single formula field and clutter up my field lists. (Or I would need to do something hacky with the formula, or use scripts/automations.) For example, say I have two tables: Articles and Authors. Articles has fields like Article Author, Article Type, and Article Cost. Authors has fields like Name, Email, and the rate schedule (News Rate, Feature Rate, Review Rate), as below: Articles Article Author – Linked record: Authors Article Type – Single select: News, Feature, Review Article Cost – Formula: ? Authors Name – Short Text Email – Email News Rate – Currency Feature Rate – Currency Review Rate – Currency Articles Written – Linked record: Articles If I want to lookup an author's email address, I can add a Lookup field and it's a good reference to have for every record in my article table. However, for an article's cost, I only want to see the relevant rate from the author's record. Currently, in order to do this, I'd need to add Lookup fields for each rate because the Formula field can only reference fields in the current table: Articles Article Author – Linked record: Authors Article Type – Single select: News, Feature, Review Article Cost – Formula: SWITCH({Article Type}, "News", {News Cost}... News Cost – Lookup: Author.{News Rate} Feature Cost – Lookup: Author.{Feature Rate} Review Cost – Lookup: Author.{Review Rate} But now I have three fields dedicated to this one formula. The fields are of no other use in that particular table and are basically clutter that I have to hide in every view. If a LOOKUP function existed, then I don't need those extra fields, and instead my formula would look something like SWITCH({Article Type}, "News", LOOKUP({Article Author}, {News Rate})... This would benefit anyone working with rate cards, inventories, or schedules (or any case where they need to perform a variable-field lookup). Another use case is doing a "deep" lookup, such as getting the country code for a phone number based on a city. Say you have a base with tables Phone Numbers, Cities, Countries; and Phone Numbers are linked to Cities, and Cities are linked to Countries; and {Country Code} is a field within Countries. Because Lookup fields in Airtable only go to one other table (you can't lookup a Linked Record field in another table and get data from that third table), you would have to add a Lookup field to Cities for {Country Code}.
... View more
Status:
New Ideas
Submitted on
Nov 27, 2024
01:53 PM
Submitted by
smullin
on
Nov 27, 2024
01:53 PM
![5 - Automation Enthusiast 5 - Automation Enthusiast](/html/@8E0586A35C6D0D07EA6A610CF7AEF6BF/rank_icons/Rank-AutomationEnthusiast.png)
Hi, I'm super excited about the new date dependency features. I've manually implemented that before with automations. However, limiting the precision to "days" seems arbitrary and limits the functionality to project management. Increasing the precision to minutes or seconds (or whatever the standard is for dates) would vastly improve utility for things like batch scheduling. Cheers, Scott
... View more
Status:
New Ideas
Submitted on
Mar 13, 2023
03:32 PM
Submitted by
Karlstens
on
Mar 13, 2023
03:32 PM
![11 - Venus 11 - Venus](/html/@A055A40C6B52EB6DE6B5684057669E1E/rank_icons/Rank-Venus.png)
Button Fields could really use an update to allow for dynamic button labeling. A label could be set to not only Single Line Text, but also support other field types such as Single Select, Link Fields, but also Attachments where an Image could be displayed as a clickable button. Here, we see each button opening a unique URL, however the label is static - locked as the text "Open URL" which is an awful user experience. Why not allow for other fields to be referenced within the Label, exactly how the URL formula works? Part of this issue stems from the URL field itself also being too simplistic, and not supporting text for the referenced URL itself (which then itself could be used by a button field, without the need for an independent Label field).
... View more
Status:
New Ideas
Submitted on
Aug 23, 2024
01:19 PM
Submitted by
Dennis_Petrou
on
Aug 23, 2024
01:19 PM
![7 - App Architect 7 - App Architect](/html/@A5FC3CBAAE60D538F9A953E47A560077/rank_icons/Rank-AppArchitect.png)
I know we can alphabetize all the options in a Multi Select field, but the field itself will display all the entries in the order in which they were selected. That should be an optional toggle, to let it display as it does currently or also alphabetically. When looking at many records at a time, and trying to compare values in a Multi Select field, it makes it very messy and difficult.
... View more