Here are a couple ideas, but this is a topic I’m sure Airtable developers could have fun with:
But if that’s too ambitious, a simple code beautifier would be sufficient. This one unfortunately doesn’t play nice with Airtable formulas because of the braces { } in fields names.
Also known as the Script Blocks editor. They have it; they just need to align all code development features to this editor.
Fund a way to expand the box in the meantime … Anybody else got issue with ’ and ' characters? - #11 by Marko.Petrovic
Just type in a very long string like ______ then edit formula and once you are done then delete. It expands it a bit horizontally.
Woučd be nice, for a start, that we can at least expand the editor (for example similar to long text field), so when we write some short simple formula we can use normal window, but when we need to write longer and more complex formulas we can expand it to ger more space. Current formula window is really small and not user frendly for except simplest of formulas.
Also error highlighting and other advances features would be great, but I think this bigger “canvas” is aspolute must, because at the moment writing longer formulas is reall pain.
Woučd be nice, for a start, that we can at least expand the editor (for example similar to long text field), so when we write some short simple formula we can use normal window, but when we need to write longer and more complex formulas we can expand it to ger more space. Current formula window is really small and not user frendly for except simplest of formulas.
Also error highlighting and other advances features would be great, but I think this bigger “canvas” is aspolute must, because at the moment writing longer formulas is reall pain.
Just an observation, but if you need really long formulas, it’s telling you something about the platform that is not ideal.
In any development environment, abstraction and business logic are essential. In addition to expanding the ability to edit complex logic, Airtable must make it possible to create and manage business logic as reusable components as:
And overall, the ability to access these logical components to perform automated changes, backups, and documentation.
Agree with this request 1000%. I currently write all of my Airtable formulas in VS Code so that I can format with multiple lines and have code highlighting. Thankfully Airtable at least preserves my formatting, but having a better formula editor is really a must-have.
Also, I’ll echo what Bill said about long formulas. There’s definitely improvements that could be made here.
I like to bump up this one, sorry to be annoying, I just hope anybody from Airtable staff is reading this enough.
Add error highlighting to formula boxes: Not just saying… “Sorry, there was a problem saving this field. Invalid formula. Please check your formula text.”
So many things are on my wishlist in terms of the formula box but this one is the #1 and it would be amazing to see something implemented soon, it’s so simple:
Add some basic error highligting and (if possible) precisely underline where the error in the formula is. Often, the error in the formula as simple syntax missing like bracket, or instead of “” there is "’ etc.
Having the formula box showing where the error in the formula is would greatly reduce the amount of time fixing the formulas.
Update: I use “CotEditor” app on MacOS so I can fix those missing brackets easier (suggestions from @Bill.French and @Justin_Barrett ), but still other characters like missing " & " causes frequent issues. It it was a complex formula, I wouldn’t expect Airtable formula editor to teach me how to write my formula but simply highlighting missing " & " in my 20 lines long concatenated formula would reduce the amount of time it takes to fix the formulas.
Just an observation, but if you need really long formulas, it’s telling you something about the platform that is not ideal.
In any development environment, abstraction and business logic are essential. In addition to expanding the ability to edit complex logic, Airtable must make it possible to create and manage business logic as reusable components as:
And overall, the ability to access these logical components to perform automated changes, backups, and documentation.
Formulas don’t have to get very long to be very prone to human error ((((((e.g., how much collective time is lost finding/fixing missing parens?))))))))))).
Formulas don’t have to get very long to be very prone to human error ((((((e.g., how much collective time is lost finding/fixing missing parens?))))))))))).
I am using CotEditor on MacOS and aside of the syntax highlighting, the best thing is it highlights the bracket pairs when you touch one of the brackets. It works in sort of similar ways as MS Excel but the brackets glow so easier to see than in Excel. Also can set dark mode, so the brackets glow is visible.
Another thing that would be so simple to fix and hugely beneficial is to show Child relationship in the Customize Filed Type box. Put somewhere another tab besides Formula / Formatting / CHILD … And clicking on these tabs will give me a listing of all the fields where this is the Parent field, that is where this field is being used for Calculation. There is the @kuovonne app Field List which was of great help to me and the app is great on its own. However, Airtable just should display the Child info in that box. That would be such an easy fix and save time to fish out all those child dependencies when I am trying to find out whether I can delete the field or not.
I am using CotEditor on MacOS and aside of the syntax highlighting, the best thing is it highlights the bracket pairs when you touch one of the brackets. It works in sort of similar ways as MS Excel but the brackets glow so easier to see than in Excel. Also can set dark mode, so the brackets glow is visible.
Another thing that would be so simple to fix and hugely beneficial is to show Child relationship in the Customize Filed Type box. Put somewhere another tab besides Formula / Formatting / CHILD … And clicking on these tabs will give me a listing of all the fields where this is the Parent field, that is where this field is being used for Calculation. There is the @kuovonne app Field List which was of great help to me and the app is great on its own. However, Airtable just should display the Child info in that box. That would be such an easy fix and save time to fish out all those child dependencies when I am trying to find out whether I can delete the field or not.
Thanks for the mention of my Field List app.
Are you suggesting that formula fields should have a list of fields that the formula itself relies on? If so, this information is available in the formula itself.
Or are you suggesting that all fields should have a list of fields that are calculated using the given field? Yes, this would be very helpful, but it is hard to say how easy a fix it would be. It would need to be present in all fields (not just formula fields), and base designers would have to be aware that fields may be used elsewhere such as apps, automations, scripts, and 3rd party integrations.
Thanks for the mention of my Field List app.
Are you suggesting that formula fields should have a list of fields that the formula itself relies on? If so, this information is available in the formula itself.
Or are you suggesting that all fields should have a list of fields that are calculated using the given field? Yes, this would be very helpful, but it is hard to say how easy a fix it would be. It would need to be present in all fields (not just formula fields), and base designers would have to be aware that fields may be used elsewhere such as apps, automations, scripts, and 3rd party integrations.
Tracking field relationships is already part of the Base Schema app, so at some level the code already exists. I’m not saying it would be an easy port to display that in a new tab in the field settings, but it’s definitely much easier than starting from scratch.
Thanks for the mention of my Field List app.
Are you suggesting that formula fields should have a list of fields that the formula itself relies on? If so, this information is available in the formula itself.
Or are you suggesting that all fields should have a list of fields that are calculated using the given field? Yes, this would be very helpful, but it is hard to say how easy a fix it would be. It would need to be present in all fields (not just formula fields), and base designers would have to be aware that fields may be used elsewhere such as apps, automations, scripts, and 3rd party integrations.
Yes, mean the second option. Like in Excel there is Dependency tracker. Or in the genealogy language, if the current view I’m looking at, the view being the parent, I’m looking for its children, not the grandparents. The grandparents are in the formula, that’s correct :grinning_face_with_smiling_eyes:
Been 6 months and still nothing. Hope more votes will get some more attention from Airtable team.
I am suggesting a simple temporary fix.
I guess it’s a lot of effort to redesign the formula editor. I understand that. In the meantime, Airtable could just at a SIMPLE fix to the problem of not knowing where the error is. Just show the position of the error in the text. Instead of saying there is an ERROR in the formula, say ERROR AT CHARACTER 123 and the number 123 represents the position of the character within the formula. (When counted from the left, the error will be on 123rd character, including spaces).
This is a VERY SIMPLE fix and many would appreciate this by saving lots of time. Yes I can use 3rd party editors, but 3rd party editors syntax doesn’t match the Airtable formulas.
This fix requires just a few lines of code. Even I could do that even I am not a programmer.
Been 6 months and still nothing. Hope more votes will get some more attention from Airtable team.
I am suggesting a simple temporary fix.
I guess it’s a lot of effort to redesign the formula editor. I understand that. In the meantime, Airtable could just at a SIMPLE fix to the problem of not knowing where the error is. Just show the position of the error in the text. Instead of saying there is an ERROR in the formula, say ERROR AT CHARACTER 123 and the number 123 represents the position of the character within the formula. (When counted from the left, the error will be on 123rd character, including spaces).
This is a VERY SIMPLE fix and many would appreciate this by saving lots of time. Yes I can use 3rd party editors, but 3rd party editors syntax doesn’t match the Airtable formulas.
This fix requires just a few lines of code. Even I could do that even I am not a programmer.
If you’re not a programmer, and especially if you have no idea what’s actually happening behind the scenes with Airtable’s formulas, you can’t say with that kind of certainty that you know how many lines of code it would take. I am a programmer, and I’m fairly confident that it would be quite a bit more than just a few lines.
From what little I know about how Airtable is developed, the formula language that we use is first converted to the actual programming language that Airtable is based upon. That means that the error is found after that conversion is complete and that other language is running tests to ensure that everything is valid. To do what you suggest, the developers would need to accurately convert back to the original formula and pinpoint the location of the error. Doing that with any degree of accuracy would be no small task.
Believe me, I would love to have that “simple” fix as much as you, but it’s not nearly as easy as you make it sound.
If you’re not a programmer, and especially if you have no idea what’s actually happening behind the scenes with Airtable’s formulas, you can’t say with that kind of certainty that you know how many lines of code it would take. I am a programmer, and I’m fairly confident that it would be quite a bit more than just a few lines.
From what little I know about how Airtable is developed, the formula language that we use is first converted to the actual programming language that Airtable is based upon. That means that the error is found after that conversion is complete and that other language is running tests to ensure that everything is valid. To do what you suggest, the developers would need to accurately convert back to the original formula and pinpoint the location of the error. Doing that with any degree of accuracy would be no small task.
Believe me, I would love to have that “simple” fix as much as you, but it’s not nearly as easy as you make it sound.
Okay. Well explained. Yes, I imagine it must be simple like it is in Excel. So I guess they need a syntax checker in the currend editor window and they don’t have one for that or they would need to do the way you explained. Now I feel more educated :winking_face:
If you’re not a programmer, and especially if you have no idea what’s actually happening behind the scenes with Airtable’s formulas, you can’t say with that kind of certainty that you know how many lines of code it would take. I am a programmer, and I’m fairly confident that it would be quite a bit more than just a few lines.
From what little I know about how Airtable is developed, the formula language that we use is first converted to the actual programming language that Airtable is based upon. That means that the error is found after that conversion is complete and that other language is running tests to ensure that everything is valid. To do what you suggest, the developers would need to accurately convert back to the original formula and pinpoint the location of the error. Doing that with any degree of accuracy would be no small task.
Believe me, I would love to have that “simple” fix as much as you, but it’s not nearly as easy as you make it sound.
I think that Airtable does some parsing before converting to the actual programming language. For example, if I have a typo in a field name, sometimes the formula editor specifically tells me that it does not recognize a specific field. The formula editor also knows what function I’m currently in and can show the parameters for that field.
Even so, I agree that overhauling the formula editor is probably a major job. It may be that Airtable has been working on it quietly behind the scenes and we will see a new editor in the coming year, … or maybe not.
In the meantime, I use a very specific style for writing my formulas with multi-lines. It doesn’t prevent mistakes in formulas (my spelling & punctuation leave a lot to be desired), but it makes identifying mistakes much easier. You can see examples of my formula writing style in almost any of my posts with formulas.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.