Release Notes

2026-07-26

The formula editor now accepts the list, decimal, true/false and escaped-text forms it previously flagged as invalid — so a calculated field that computes correctly also validates correctly.

✅ The formula editor accepts the formulas it always ran

If you build calculated custom fields, you may have hit this: a formula that computes correctly still showed as invalid in the editor, so the preview refused to run.

The editor now understands the full formula syntax, including:

  • ListsSUM([${itemEstimate}, ${itemLikelyEstimate}]), CONCAT([${itemTitle}, ${itemNumber}]). This is the form most functions use for a range, and it is what the built-in examples insert when you pick a function from the suggestions.
  • Decimals0.5 * ${itemEstimate}.
  • True/false and empty valuesIF(true, 'Yes', 'No'), COUNTA([1, null, 3]).
  • Text with escapes — apostrophes and line breaks inside quoted text, such as 'it\'s ready'.

Existing calculated fields are unaffected: every one of them computes exactly the same value as before. This corrects what the editor would accept, not what a formula means.

📚 Learn more: Setting up custom fields