Empty data field not handled correctly by Advanced Search 'Is not'

• 01-12-2010, 11:12 AM

  16088

  FlatRockStan Joined about 3 years ago Posts 8

  Empty data field not handled correctly by Advanced Search 'Is not' Reply Quote We have a member database radio button field (Internal use by Admins only, with 2 choices - Pending and Completed).  When a new record is created, as far as I can tell, there is no capability to set a default value, so until a radio button choice is made, the field is Empty. Would prefer database to use a default field value (the one checked in Settings would make sense), but it gets worse.  When we do an Advanced Search for <thisfield> 'Is not' 'Completed', the records listed DOES NOT include those Empty values.  Seems like they should be since the field clearly does not = 'Completed'.  Bug or feature, this is bad. Are we doing something incorrectly? Fix needed?

  Report abuse

• 01-14-2010, 1:24 PM

  16145 in reply to 16088

  jim Joined about 4 years ago Toronto Posts 533	Re: Empty data field not handled correctly by Advanced Search 'Is not' Reply Quote You are right, this is an oversight on our part in the way these internal fields are handled. We have now added this on our list of enhancements for future releases. Jim Sympathy, Fluid Apricot
  	Report abuse

• 11-06-2011, 10:21 PM

  24076 in reply to 16145

  Jennn Joined about 7 months ago Posts 38

  Re: Empty data field not handled correctly by Advanced Search 'Is not' Reply Quote Ditto, same problem with an admin-only radio field. We need to be able to set a default value. As it is, we end up with new members with null values (making the field mandatory doesn't help).   The only way to find them is to get the excel output and sort it. Advanced search should allow searches for null values in radio fields.

  Report abuse