As you all know, the formula field is a versatile field that enables you to perform varied computations, from simple math to concatenation to field value comparisons.
What's the change?
Previously, if the value of a participating field was empty, the formula field considered its value to be "0". This is logically incorrect, as zero is a value, whereas null/blank is the absence of a value, which are not the same. This has resulted in erroneous calculations.
We've fixed this behavior.
Henceforth, any formula field without a value will not be computed. The returning value in the formula field will be blank.
Let's understand using an example.
Zylker storage is a physical unit that rents out storage spaces. To help visitors know the price beforehand, Zylker has configured a formula field.
Formula: Rent= No. of storage units * price * duration
Syntax: (${Leads.Price per unit}*${Leads.Number of units}*${Leads.Period of storage required})
As you can see from the image, the "Period of storage required" or duration field is empty. CRM used to consider no value to be 0 and returned 0.
After the update, the rent field will be blank, per the corrected logic.
In cases where the zero or blank value doesn't impact the output (for example: addition), the calculated output will consider a lack of input as zero.
Formula: Rent= (No. of storage units * price * duration) + tax
Syntax: (${Leads.Price per unit}*${Leads.Number of units}*${Leads.Period of storage required})+${Leads.Tax}
In the above image, you can see that even if the tax field is empty, it doesn't hinder the calculation, and so the formula calculates the rent in this case.
That's all for this announcement. We'll roll this behavior out to all users in all DCs shortly. To learn more about formulas, read
Building Formula Fields .