Search found 10 matches

by ivandevpartner
Tue Dec 24, 2019 6:11 am
Forum: Bullhorn APIs
Topic: Querying data with JPQL
Replies: 0
Views: 241

Querying data with JPQL

Hello, Reading through the docs on using the "query" mechanism on some entities, it states that the conditional clause ("where") uses JPQL. I have tried unsuccessfully to get a Note from BH REST API that has a placement with a certain Id. I simplified the query to return the Notes that have one plac...
by ivandevpartner
Tue Jul 09, 2019 7:38 am
Forum: Bullhorn APIs
Topic: Missing and reappearing records
Replies: 6
Views: 1608

Re: Missing and reappearing records

We had and still have that same behaviour.... Never found the source of the issue.
As far as I know this issue was present at least as far back as autumn 2017.
Unfortunately no real fix or workaround found.
by ivandevpartner
Tue Jul 09, 2019 7:26 am
Forum: Bullhorn APIs
Topic: Missing events from subscriptions
Replies: 0
Views: 2736

Missing events from subscriptions

I have a problem with a different number of events arriving to two identical subscriptions. I have two environments set up in my application (Live and Dev) that both have exactly the same number of entities in their subscriptions. As of right now, I'm in a situation where DEV has received and proces...
by ivandevpartner
Fri Apr 05, 2019 3:32 am
Forum: Bullhorn APIs
Topic: ClientContact and its history
Replies: 0
Views: 2977

ClientContact and its history

I have a number of ClientContacts whose status is different from the one recorded in their latest UserEditHistory->UserEditHistoryFieldChange. I filter userEditHistory data by the "personSybType" field having the "ClientContact" value and the userEditHistoryFieldChanges by the "columnName" being equ...
by ivandevpartner
Fri Feb 08, 2019 9:32 am
Forum: Bullhorn APIs
Topic: OpportunityHistory vs OpportunityEditHistory
Replies: 3
Views: 3650

Re: OpportunityHistory vs OpportunityEditHistory

Thanks for the reply.
I am interested in the status field so looks like the simple OpportunityHistory approach would be a bit more straightforward.
However it is still unclear to me why the values of the "status" field are not the same in the OpportunityHistory and the Opportunity itself.
by ivandevpartner
Wed Jan 30, 2019 11:30 am
Forum: Bullhorn APIs
Topic: Tracking ClientContact changes
Replies: 3
Views: 2915

Re: Tracking ClientContact changes

Thanks for the info. I have hit a small problem with pulling changes for ClientContacts specifically. The following request gives me an error on my targetEntity filter: query/UserEditHistory?where=(dateAdded>=946677600000)AND(dateAdded<=1577829600000)AND(targetEntity._subtype=ClientContact)&fields=t...
by ivandevpartner
Wed Jan 30, 2019 10:11 am
Forum: Bullhorn APIs
Topic: OpportunityHistory vs OpportunityEditHistory
Replies: 3
Views: 3650

OpportunityHistory vs OpportunityEditHistory

Hello, I have noticed that the API supports calls to OpportunityHistory and OpportunityEditHistory + OpportunityEditHistoryFieldChanges tables. Bh docs, at least as far as what I dug through, do not specify the difference between those two tables in terms of history keeping logic. Some opportunities...
by ivandevpartner
Fri Jan 25, 2019 11:37 am
Forum: Bullhorn APIs
Topic: Pulling date limited data from JobOrderEditHistoryFieldChange table
Replies: 2
Views: 2220

Pulling date limited data from JobOrderEditHistoryFieldChange table

Hello, Can anyone help me with the concept of pulling data from JobOrderEditHistoryFieldChange table that has been changed or added within a specific time frame? Ideally I'd like it to be something like this: /query/JobOrderEditHistoryFieldChange?where=(dateAdded>=946677600000)AND(dateAdded<=1577829...
by ivandevpartner
Fri Jan 25, 2019 11:32 am
Forum: Bullhorn APIs
Topic: Tracking ClientContact changes
Replies: 3
Views: 2915

Tracking ClientContact changes

Hello, I would like to know if there is any entity that holds the history of changes done do ClientContacts, specifically the "status" field. Some entities support {Entity}EditHistory and {Entity}EditHistoryFieldChange tables to track field changes, but it looks like ClientContact is not one of them...