ZipCodeGis Entity - 02309322

Forum for users and developers of Bullhorn's new REST API service.

Moderators: StaffingSupport, s.emmons, BullhornSupport

Post Reply
max_max_mir
User
Posts: 77
Joined: Tue Jun 22, 2010 4:25 pm

ZipCodeGis Entity - 02309322

Post by max_max_mir » Sun Aug 14, 2016 12:17 pm

Is ZipCodeGis a new entity, and if not, is it a custom entity? There are two problems with this Entity

1. id is of type String with maxLength 2147483647 (id is Integer for all other entities, so why is it a String for this, especially with such a large value for maxLength?)

2. When I try to query this entity, I get the following error

Code: Select all

java.lang.ClassCastException: java.math.BigDecimal cannot be cast to java.lang.String
- Y

mparkinson
User
Posts: 1
Joined: Tue Aug 16, 2016 11:00 am

Re: ZipCodeGis Entity - 02309322

Post by mparkinson » Tue Aug 16, 2016 12:24 pm

Hello max_max_mir,

ZipCodeGis is a database view used as a Zip Code lookup table within the Bullhorn application - containing Zip Codes and their relative locations in respect to latitude, longitude, and country/city/state.

This view however is not a documented Entity for use independently via the REST API. The available entities are documented in the link below at http://developer.bullhorn.com:

http://developer.bullhorn.com/sites/def ... TAPI_0.pdf

If your intent was to have a queryable lookup list of zip codes/addresses via the API, e.g. "what is the latitude/longitude of Zip Code X", you'd need to use a different service for that purpose, but if there was a different business objective in mind where an alternate entity/API call may potentially be suitable just post back in the thread.

Morris
Morris Parkinson
Enterprise Support Analyst
B U L L H O R N
Staffing and Recruiting Software, On Target, On Demand
Bullhorn Support Contact Numbers
US: 617-478-9126
UK: 44 800 032 2848, ext. 1
Australia: 61 28 073 5089
International: 617-478-9131

max_max_mir
User
Posts: 77
Joined: Tue Jun 22, 2010 4:25 pm

Re: ZipCodeGis Entity - 02309322

Post by max_max_mir » Wed Aug 17, 2016 6:07 pm

Thanks Morris. This entity showed up when I ran a query requesting all entities. Any reason why this cannot be suppressed from the query? Sometimes the documentation is a little out of date, so I was left wondering why this new entity was showing up in my queries that wasn't showing up before.
- Y

Post Reply