Hey Bullhorn support, I am encountering an incorrect behaviour from your side when filtering with datetime columns. For example, see the JSON below: { "where": "isDeleted = false AND (dateLastModified < 1464452509857)", "fields": "id,codeIdentifier,dateLastModified,description,goalPeriodId,goalTypeI...

I am sending a POST request to https://rest33.bullhornstaffing.com/rest-services/xxxxx/query/ZipCodeGis with the following request body: { "where": "id is not null", "fields": "id,areaCode,city,countryID,latitude,latitudeActual,longitude,longitudeActual,state", "count": 500, "start": 0 } and the res...

I sent a POST request to https://rest33.bullhornstaffing.com/rest-services/xxxx/query/JobBoardPost with the following JSON in the body of the request: { "where": "id is not null", "fields": "location", "count": 500, "start": 0 } The issue happens only when the field 'location' is included to fields....

This is also happening on my case.

Hi Colin, Are you sure the id:[100 TO 200] syntax will work as expected? I am trying similar queries on Candidate entity and it looks like Lucene ranges works only for string comparison, not numeric. Which means, id:[100 TO 200] will also return records with id=1500 because 1500 is between 100 and 2...

Hi,

I can confirm the same issue as the one doubledash mentioned.

In a private/incognito window the login page is shown successfully, otherwise a 500 internal NullPointer Exception is thrown in your servers.
Is there some misconfiguration we did or is this a bug?