Quick Tip: When using Calculated Field in your Business

Aware of OOB Calculated Fields! That’s right when your Calculated field involves 2 or 3 fields then you need to be aware of below scenario:

Suppose we have below fields on the Account record:

Sum A, Sum B, Sum C and the calculated fields Sum of A, B, C and A part by B(A/B).
Sum of A, B, C is calculated as Sum A + Sum B + Sum C;
A part by B(A/B) is calculated as Sum A / Sum B;
What if the any of the fields involved in the calculation is null or Zero in case of Division?

Scenario: If any of the field is null for Addition

So, Sum A = 3, Sum B = 3, Sum C = null,
The expected result is 6.

But CRM handles it in different way. It ignores the calculation and sets the calculated field to null as you can see above.

This was one of the concerns which Business raised as it was not properly ignoring the null values. So later we found that this is the OOB behavior of Calculated fields.
Scenario: If Denominator is ‘0’ involved in Division

Sum A = 4, Sum B = 0;
A part by B(A/B) = null
It does not give error. It simply ignores and sets the calculated field as null.

Recently we faced this scenario. So, after searching we got the below Option which could avoid this scenario.

Create a Business rule of Scope = Entity and try to set the Default values of the fields involved in the calculation so that it will always calculate.
Hope this helps and adds to your knowledge.