Right now, if you have two calculated fields, and one is using the other to generate it's sum. If the first field does not have a value (IE: a rolllup of associated deal values to a company, before any deals are created for that company), then the dependant field will be null as well, even if the first field is being subtract from some other value. For example, what we are experiencing is similar to:
x = first_calc_field 1000 - x = null <-- This is what happens 1000 - x = 1000 <-- This would be preferable If it's not the default, than just a boolean that we can select for if we want the value to default to 0 instead of null would be great, so that we can build additional calculations off of it.
...read more