It would be awesome if Airtable’s formula engine could recognize “curly quotes” as the same thing as "straight quotes". When editing formulas on mobile web browsers, curly quotes are the default. And, when copying and pasting formulas that have curly quotes from other places — such as this forum, which changes quotes to curly quotes outside of a code block, or rich-text editing apps which change quotes — the formulas won’t work upon pasting them into Airtable. There have been multiple times where I have been scratching my head in confusion over a “seemingly-perfect formula” that doesn’t work properly, but it is actually failing because the quotes are curly. ... View more

I’d love a NORMALIZE and STANDARDIZE functions. ... View more

So this is strange… In Airtable’s formula field reference, several of the examples refer to fields that don’t exist anywhere within the example itself. For example, check out this example that was given for the WORKDAY_DIFF function: WORKDAY_DIFF({Assignment date}, {Due Date}, '2017-09-04, 2017-10-09, 2017-11-10') => 8 Okay, that’s great that the formula results in 8, but we can’t truly understand the formula if we don’t know what the values are for “Assignment Date” & “Due Date”. Interestingly, we also can’t tell whether the dates are in YYYY-MM-DD format or YYYY-DD-MM format. Yes, we can type up this formula in our own database and play with it ourselves, but if we’re just reading through the formula field reference, it leaves more questions than it answers. For example, my immediate question about this formula is whether this formula includes the start date & the end date as part of its “count”. Same problem with this function: IS_SAME({Date 1}, {Date 2}, 'hour') => 0 Huh? Why does this result in 0? What are Date 1 and Date 2? And this function: WEEKNUM({Date}) => 46 Why does this result in 46? What was the original date? And this function: WORKDAY({Launch date}, 100, '2017-09-04, 2017-10-09, 2017-11-10') => 6/20/2017 Why does this result in 6/20/2017? What was the Launch Date? But there are many more examples — just like these — in the formula field reference. We can’t truly understand the functions properly from the formula field reference unless we understand which inputs you’re putting into the functions. Yes, I get it that we can just play around with these functions ourselves in our own tables and figure this all out on our own, but it would be really nice to have a fully fleshed-out reference guide that we can fully comprehend. ... View more

There are discrepencies with Rich Text content causing issues. If I copy/paste a rich text field into another rich text field, then create a formula that checks to see if they are equal: IF({Rich Field 1} = {Rich Field 2}, "SAME", "NOT SAME"), then it shows these as being equal. But if I take the content from {Rich Field 1} via the API, and perform an update via API to {Rich Field 2}, the formula comparison says they are NOT SAME. Even though if I compare them from the API they have the exact same values. So something not working when pushing via API to reflect same underlying content. ... View more

Currently, when you delete a field, it breaks any formulas that referred to that field. When the user views the broken formula, the field name is replaced by a non-human-readable string. Thanks to the scripting API, we can now see that the non-human-readable string in the broken formula is a concatenation of a literal string and the field id of the deleted field "column_value_" & fieldIdOfDeletedField I suggest that the string also concatenate the name of the deleted field "column_value_" & fieldIdOfDeletedField & "_" & ENCODE_URL_COMPONENT(fieldNameOfDeletedField) This would make fixing broken formulas much easier because the user could see what the original formula was. The scripting API shows that the field definition for a formula field stores an array of referencedFieldIds. Could that array also somehow store referencedFieldNames? After all, the field definition for a multipleRecordLinks stores both ids and names. And now for an example … Say the field {dog age in human year} had the formula {dog age in calendar years} * 7 If the field {dog age in calendar years} is deleted, the broken formula now looks like {column_value_fldFRA5nV1QBtrtLi} * 7 I would like the broken formula to look like {column_value_fldFRA5nV1QBtrtLi_dog+age+in+calendar+years} * 7 or {column_value_fldFRA5nV1QBtrtLi_dog%20age%20in%20calendar%20years} * 7 By the way, for all you dog lovers out there, I know this formula is not really accurate. I am just using it to illustrate a point. ... View more

It would be useful to be able to use a whole column as an array to use for Numeric functions. For example I could use a formula that shows how much variance there was in a number field from the Average, Max or Min of that field. Basically it would be the same functionality that is in the Summary Bar, but available in functions. ... View more

I wish I could write formulas with line breaks so that it’s easier to read, comprehend, and modify. For instance, I wish the first formula could be written like the second. It currently returns an error. Current: IF(FIND( “engineer”,LOWER( {Collateral Title})) > 0, “Engineer”,IF(FIND( “engineer”,LOWER( {Overview / Short-form content} )) > 0,“Engineer”,IF(FIND( “engineer”,LOWER( {Preloaded Topic} )) > 0,“Engineer”,IF(FIND( “coding”,LOWER( {Collateral Title} )) > 0,“Engineer”,IF(FIND( “coding”,LOWER( {Overview / Short-form content} )) > 0,“Engineer”,IF(FIND( “coding”,LOWER( {Preloaded Topic} ))>0,“Engineer”, IF(FIND( “developer”,LOWER( {Collateral Title})) > 0,“Engineer”,IF(FIND( “developer”,LOWER( {Overview / Short-form content} )) > 0,“Engineer”,IF(FIND( “developer”,LOWER( {Preloaded Topic} )) >0,“Engineer”,""))))))))) Desired: IF(FIND( “engineer”, LOWER( {Collateral Title})) > 0, “Engineer”, IF(FIND( “engineer”, LOWER( {Overview / Short-form content} )) > 0, “Engineer”, IF(FIND( “engineer”, LOWER( {Preloaded Topic} )) > 0, “Engineer”, IF(FIND( “coding”, LOWER( {Collateral Title} )) > 0, “Engineer”, IF(FIND( “coding” , LOWER( {Overview / Short-form content} )) > 0, “Engineer”, IF(FIND( “coding”, LOWER( {Preloaded Topic} ))>0, “Engineer”, IF(FIND( “developer”, LOWER( {Collateral Title})) > 0, “Engineer”, IF(FIND( “developer”, LOWER( {Overview / Short-form content} )) > 0, “Engineer”, IF(FIND( “developer”, LOWER( {Preloaded Topic} )) >0, “Engineer”, “”))))))))) ... View more

Having left Airtable a while ago I thought I would check back in to see if they had implemented these two features yet? Sharing between bases has been requested from long before I even knew about Airtable, I think the dinosaurs were around when that first got requested, any news? Will it happen? Do they still ignore requests? Another request was for using regex in formulas, any news on this? ... View more

Please include “countif” and “sumif” functionality on the roll-up field reference. The “if” criteria could either be written manually or even better you could have an additional dropdown where you tick the relevant data you want summed or counted. This would be incredibly useful. Thanks! ... View more