We have a globally searchable custom field with values like 12345-1, 12454-2, etc. Basically, a series of random numbers with a hyphen (in some cases). If we search 12345, the 12345-1 record isn't captured. We have to add the hyphen to recognize 12345-1. I'm trying to understand why is that the case. 12345- isn't even an exact match but it captured 12345-1 record. What makes 12345 (no hyphen) not work?

We run into the same thing with our item numbers which is a real headache. All our items are 123456789 and sometimes have a variant of 123456789-GRN or -BLU . But we get reports all the time of “item doesn’t exist because it doesn’t find it without the dash”. Super annoying We end up having to use % in front of everything which I know doesn’t answer your question but you know misery loves company I guess

Thanks, @AI1. That's also the workaround we found. If it helps, I read that hyphen can also be used as an OR operator. But I still don't understand it. So, 12345- is interpreted as 12345 OR (what? I don't have any character after the hyphen when searching)?