SAP Knowledge Base Article - Public

3215638 - Candidate search functionality not fetching expected results when using "Division" field as filter from "Basic Info".

Symptom

When trying to fetch results from the Candidate Search functionality using "Division" field as a filter from "Basic Info", and using "contains", the search outcome does not provide the expected result of candidates matching the criteria.

This happens even when the Privacy option chosen by the candidate is "Any company recruiter worldwide" and the Field type for division is "Text".

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

Environment

SAP SuccessFactors Recruiting Management

Reproducing the Issue

  1. Go to Recruiting.
  2. Select Candidate.
  3. Choose "Division" from "Basic Info" and use "contains".
  4. fill in the Criteria in front of "contains".
  5. Hit Search.
  6. Search result does not fetch entire list of candidates matching the search criteria.

Cause

The field division is a text type field in Solr. It is expected that the value when stored in Solr is tokenized and when searching it matches the tokens for the results.

Resolution

The search results will not match the filter criteria when using the "Candidate search"  functionality for "Division" field, whose type is Text in Solr.

This is an expected behavior of the Product.

Whereas, "starts with" and "is exactly" filters in advanced search produces matches even when the actual phrase doesn't start with or is exactly the search term.

For example, the search term "reserve" with filter exactly or starts with will produce match for values "reserve list", "not in reserve list" etc. 
This is because Solr tokenizes these values during index creation and the filters "starts with" or "is exactly" is applied per token (ie per word). As the text search engine finds an exact word match or a word that starts with the term in the particular field, a match is returned.

The same behavior can be observed in other fields like first name or last name. For example, if a candidate has "Billie Jean" as first name, then a search with "Jean" and "is exactly" or "starts with" filters would return the candidate.

This is an expected behavior for searching through the text fields. 

Keywords

Candidate, search, division, type, text, Solr, contains, advanced, privacy , KBA , LOD-SF-RCM-CAN , General Candidate Issues (not Offers, not Profiles) , Problem

Product

SAP SuccessFactors Recruiting all versions