Dynamics 365 CommunityForums Microsoft Dynamics CRM (Archived) Calculated fields and ...

Calculated fields and null values

(0) Share

Report

Posted on by Cyclefitness

The Dynamics constraint that will not allow a calculated field to calculate if any of the fields in its formula have a null value is causing me quite the issue.

I had business rules set at the scope of form level to set to 0 if null, but that doesn't seem to be working consistently with imported records. So, I tried changing the scope to "entity" thinking it would be a database-level default. But, again, it isn't updating the value on records that already exist which were imported.

So ... I did a google search and came upon a post to create a calculated field for each field in the formula which will set the value to 0 if null, then use those in the formula. So ... it would look like this:

Calculated Total $ = (Calculated Unit $ * Calculated # Units)

However, my Calculated Total is used in rollups on two other entities. Dynamics will not allow this.

How else can I solve this?

*This post is locked for comments

All responses (1)

Answers (0)

Cyclefitness on at

Like (0)

Report
RE: Calculated fields and null values

To re-summarize:

An "entity" level business rule which states; "If field is null, set to 0" is not setting the field to 0 when retrieving the record. What triggers this update?

A Calculated Field using calculated fields as factors, isn't available to use in a rollup field. Could this be because the SourceTypeMask attribute is wrong? The calculated field is not referencing anything other than calculated fields on the same entity.