We were using the Lucene search with entity type Candidate and requesting the top two results for a search by email address, to check that a) a candidate record existed with that address and b) it was unique. (If the the top result was an exact match and the second wasn't, we assumed success.) We then copied the Bullhorn ID to our candidate record so that future CVs, profile updates and so on made by the candidates could be sent to Bullhorn.
All was working fine up to and including 7 October. From today, 9 October, we get the following message: 'Corporation XXXX has no CANDIDATE index'. There were maintenance Bullhorn maintenance updates on the evenings of 7th and 8th October so I assume one of those removed this index. No code changes on our end for several months.
I know that Candidate is not listed as one of the entities available in the Lucene search but if there's any way of re-enabling this index, it would be much appreciated – it was a solid and easy way of checking of matching records for candidates who signed up before we wrote our Bullhorn-Wordpress plugin. We're on CLS22. Can supply account details if you think there's a chance of getting this very useful approach working again.
When it comes to the useV2=true fix we released an update to the system that should help get around this on Monday, October 18th in the evening U.S. time.
We were trying to revert so that this useV2 would stop impacting REST calls. If you are still seeing the issue I recommend getting in touch with our support team by calling or submitting a ticket as if the issue is still present getting in contact with support that way could provide a quicker turn around.
We are still analyzing post hot-fix, however, to make sure everything is running properly.
Hope that helps,
Enterprise Support Analyst
B U L L H O R N
Staffing and Recruiting Software, On Target, On Demand
617-478-9126 (US Support)
+44 800 032 2848 ext. 9131 (UK Support)