I'm trying to query candidates by secondarySkills using a lucene lookup query.
like this:
{rest_url}/{corp_token}/search/Candidate?orderBy=id&count=50&fields=id,name&start=0&BhRestToken={rest_token}&query=primarySkills.id:"^name='2D CAD'"
However I'm getting an error:
{u'errorMessage': u'Search failed: Bad Query: Cannot parse \'(aclIsPrivate:0 OR aclOwnerId:{owner_id_redacted}) AND (primarySkills.id:"^name=\'2D CAD\'")\': Cannot get field meta for \'primarySkills.id\'.'}
The documentation states you can only use lookup queries for fields with "lookupNames" but if I query the candidate entity for metadata like this:
{rest_url}/{corp_token}/search/Candidate?BhRestToken={rest_token}
it comes back with this for primarySkills.id:
{
u 'type' : u 'INTEGER',
u 'name' : u 'primarySkills.id',
u 'isSortable' : True,
u 'lookupNames' : [{
u 'names' : [u 'name']
}]
},
So this should be possible? Am I missing something obvious?
Candidate /search via secondarySkills.id lookupNames
Moderators: StaffingSupport, s.emmons, BullhornSupport
Re: Candidate /search via secondarySkills.id lookupNames
Hello iforshaw.
If you're attempting to query candidates by "secondarySkills", I cannot see why you are using the field "primarySkills" in your /GET call. Also, if you are going to query on .id, the command requires a number be added for the ID.
Please use this format for querying for candidates by their secondarySkills:
{corp token}/search/candidate?query/where=secondarySkills.id:####
I hope this helps!
If you're attempting to query candidates by "secondarySkills", I cannot see why you are using the field "primarySkills" in your /GET call. Also, if you are going to query on .id, the command requires a number be added for the ID.
Please use this format for querying for candidates by their secondarySkills:
{corp token}/search/candidate?query/where=secondarySkills.id:####
I hope this helps!
Re: Candidate /search via secondarySkills.id lookupNames
Can we add multiple skills id in the search query ??


