Domain check has trouble with NULLs

[TerriWaddell1]

Hello,

I am running the Data Reviewer domain check on an address point feature class.  In the feature class, numerous fields use domains but may also allow Null values.  Examples:  unit type (which is only used for specific address types); HALF (which is old-style 1/2 addresses), among others.  IF there is a value for the field, it must come from the domain, but it can be empty as well. When I run the check, I do NOT have the "Search for Null Values" option checked. 

Data Reviewer keeps flagging two fields as having "invalid domain values", while it seems perfectly happy with blanks  in other fields.  When I look at the table, most of our optional fields are "blank" (I.E. no NULL or <NULL> there, just empty white space in the table).  However, it appears that at least for some fields, Data Reviewer wants NULL instead of a blank. I am trying to figure out how to get Data Reviewer to stop caring about NULL versus blank, or if that is not possible, how do I get the database set up to automatically fill in NULL if there is no data (at least on new records). 

Any advice is appreciated, I'm starting to get a permanent indent on my forehead from banging it against my desk!

[MichelleJohnson]

Blanks are different than NULLs.  Data Reviewer will return blanks as errors if there is a domain assigned to that field.  You can select all the blanks and bulk update it to NULL, which I normally do in the attribute editor.  Once you have your feature selected, highlight the feature class in the attribute editor and enter <NULL> into the field that has the blanks.  This should update all records in the table.  You should now see <Null> in that field.

michellej.

[TerriWaddell1]

I understand that I can update the attributes with a field calculator, however all new records have this problem which means I have to constantly run field calculates just to get Data Reviewer to stop flagging these issues.  I need a way to tell Data Reviewer not to look for this problem at all.  I've tried to exclude the problem fields from the domain check but nothing I've tried has worked.