Hi,

Please see attached screen shot. This is a DevExpress grid populated from a stored proc. All the fields from the left, up until the column with 999, are "required fields" in the BO. The ones to the right of the 999 are not. The bottom panel shows the data that is returned by the stored proc.

I changed the value in the 4th column from 100 to 3100 and clicked Save. This fired a Broken Rule on the 5 marked columns saying they are 'required'. From the database listing you can see the checkboxes with errors have a value of False (0) and the column second from the right (which is an integer column) also has a value of 0.

If I change the integer column from 0 to 1 the broken rule goes away for that column. If I then change the column back to its original value of 0 the broken rule still doesn't fire. However, the same process does not work for the checkboxes, i.e. ticking a checkbox to True stops the broken rule from firing but once it is ticked back to False the rule fires again.

Cheers, Peter

They are considered "real values", they are just considered to be empty. 

When we test on values within the business object, we generally use the .Item property, which evaluates the strong-typed properties of the subclass and returns the values.  So, .Item("ATTLookUp") will call the Get of the ATTLookUp property.  So, when testing default values, since most columns are .NET value types (not reference types), we have to test on the "default" value for a value type (because value types always have a value).  We do test on DBNull.Value from the CurrentRow("ATTLookUp") to test required fields as well, but we also have to test on the default for value types, so 0 and False are considered to have not been set.  Generally, you won't want to use the RequiredFields for a Boolean property, you'll want to test the CurrentRow("FieldName") Is DBNull.Value on your own.