It can be really difficult to troubleshoot broken formulas in Airtable, because the error message only tells us that something went wrong — but it doesn’t tell us WHERE something went wrong.
In most other programming languages, the error handling will either:
- Highlight the part of the formula that is broken.
- Or tell the user the exact line number & character number of where the formula is broken.
Either one of these scenarios would be fine! 🙂
This product suggestion was inspired by this thread:
No, this is not true. For example: IF( 3 > 0, "yes", "no" ) will evaluate just fine. But IF ( 3 > 0, "yes", "no" ) will result in an error. I have never before worked with a single programming language that would get hung up on that extra space there! However, this is where things gets really strange. Because Airtable got hung up on that extra space up above, you would think that it would get hung up on an extra carriage return — but it doesn’t. For example, this function evaluates ju…