Menu
Articles in this section
Custom Calculated Fields: FAQ
Short answers about how calculated fields behave. For creating one, see Custom Fields Guide, Calculated fields.
Which plans include calculated fields?
Enterprise only.
Which objects can have a calculated field?
Contacts, organizations, opportunities, leads, projects, and custom objects.
How many custom calculated fields can I create?
Up to 20 per object.
What programming language is used to create custom calculated fields?
C# (C sharp), consistent with validation rules. Formulas can use IF statements but cannot contain for loops, do while loops, or method declarations.
When are custom calculated field values actually calculated?
Instantly on the record. Saving a new or edited formula also starts a background process a few seconds later that recalculates every existing record, with record change notifications suppressed so nobody is flooded.
Can users edit a calculated field’s value?
No. A calculated field is read-only; its value comes from the formula.
Can I create a calculated field that contains other calculated fields?
No, this is not currently possible. Formulas cannot be layered; each must stand alone.
Why won’t my calculated field save?
It has to return a value and the formula has to validate. The reason for a failure is shown above the formula field. See Creating a calculated field.
How do I avoid a divide-by-zero error?
Numeric fields default to 0, so guard any division with an IF that returns 0 when the divisor is 0. There is a worked example under Division.
Can editing a calculated field trigger workflow automation?
Only if you check trigger any related workflow automation processes on the edit screen before saving. It is unchecked by default. See Editing a calculated field.
Are changes to calculated fields recorded in Field History?
No. Formula fields are among the field types the audit log does not capture. See What is not tracked.
Related to