Affects Version/s: None
Fix Version/s: 1.5
As reported by Dave Jenkins. Pls verify. If recreated - fix, else get back to Dave J. to request more info, etc.
This is related to our modification in how we store multi-value custom data (e.g. checkboxes and multi-selects). The new datastore model is [Ctrl-A]4[Ctrl-A]14[Ctrl-A] - rather than 4[Ctrl-A]14 .... so searches for option 4 should actually look for [Ctrl-A]4[Ctrl-A] which eliminates false positives. According to dave, this isn't working...
---- original post ----
I'm hoping this will be fixed by
> > Checkbox and
> > Multi-select Fields - Store and Handle Leading and
> > Trailing Delimiter
> > (Ctrl A)" but wanted to confirm this; otherwise I'll
> > post a bug report.
> > I have a custom field set up as Alphanumeric,
> > CheckBox. There are 18
> > options, with values "1" - "18". When I search on
> > the term with value
> > "1" ("Advice"), it incorrectly picks up contacts
> > that don't have Advice
> > selected but do have e.g. "Play", which has value
> > "14". The "char_data"
> > field for one contact that incorrectly matches on
> > "1" is "4[Ctrl-A]14".