Note Updation - Person Preference is not updated properly

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

Moderators: StaffingSupport, s.emmons, BullhornSupport

Post Reply
mahadev
User
Posts: 18
Joined: Fri Jun 21, 2019 8:03 am

Note Updation - Person Preference is not updated properly

Post by mahadev » Mon Jun 24, 2019 3:44 am

Hi Team

I created Note with person_preference (lead id :16419 ) and updated with person_preference (lead id :5465 ) through Rest API.

But This note is under l6419 lead summary page , not 5465 lead summary page . But in edit page , it showing correct lead .

Rest API :

Create API :


PUT /rest-services/1s2o10//entity/Note?BhRestToken=....

Code: Select all

{"comments":"Comments","minutesSpent":90,"action":"ClientVisit","personReference":{"id":16419,"type":"Lead"}}
Update API

POST /rest-services/1s2o10//entity/Note/59761?BhRestToken=......

Code: Select all

{"comments":"Comments","dateLastModified":"06/21/2019","isDeleted":false,"jobOrder":null,"minutesSpent":90,"name":null,"action":"ClientVisit","externalID":null,"truestDateAdded":"06/21/2019","commentingPerson":{"id":373,"type":"CorporateUser"},"personReference":{"id":5465,"type":"Lead"}}
Why this note still showing under 16419 Lead ?
Attachments
Bullhorn.png
Bullhorn.png (71.04 KiB) Viewed 775 times
Bullhorn (1).png
Bullhorn (1).png (46.66 KiB) Viewed 775 times
Last edited by mahadev on Thu Jul 18, 2019 2:28 am, edited 1 time in total.

mholmemi
User
Posts: 17
Joined: Fri Feb 15, 2019 10:31 am

Re: Note Updation - Person Preference is not updated properly

Post by mholmemi » Mon Jun 24, 2019 9:47 am

Hi mahadev,

This is Mikaela from Bullhorn Support. This is might be an indexing issue. I would recommend trying to re-save the record. If that doesn't work, can you please provide your username so that I can investigate further?

Thanks!
Mikaela
Mikaela Holme-Miller | Tier II/Enterprise Support Analyst

mahadev
User
Posts: 18
Joined: Fri Jun 21, 2019 8:03 am

Re: Note Updation - Person Preference is not updated properly

Post by mahadev » Tue Jun 25, 2019 6:34 am

Hi Mikaela,
Thanks for your reply. I tried to resaved the record, still issue exist.can you investigate more and let me know you want any details from my side.

User name: mahaDev

rkaruppusamy
User
Posts: 8
Joined: Fri Sep 30, 2016 7:49 pm

Re: Note Updation - Person Preference is not updated properly

Post by rkaruppusamy » Mon Jul 15, 2019 10:06 am

I am also facing the issue. Can you please provide an update asap?

kschutten
User
Posts: 17
Joined: Tue Jun 25, 2019 2:22 pm

Re: Note Updation - Person Preference is not updated properly

Post by kschutten » Mon Jul 15, 2019 1:35 pm

Dear Bullhorn Support,

I also tried to update to another Lead and Candidate via API and I am facing the same results for both.

Insert as lead id: 16419
Update to lead id: 5465

GUI
1. It's still showing under tab notes of "16419", probably because there suddenly is a new "Additional Reference" in the note (gui)
2. Although it is showing "5465" in the note itself, it's missing under tab notes of "5465"

API data: (... /entity/Note/{noteid}?fields=id,personReference,people(id) )
3. "personReference" is updated properly to "5465".
4. The reference to "people" (or "entities)" does seem to be updated differently from the gui or API insert.
a. Only "16419" showing in the API data under "people"
b. "people" is missing a reference for "5465"
c. When I (re)save the note in the gui, both "16419" & "5465" are showing in under "people"

Please note that the results are the same for both leads and candidates!

kschutten
User
Posts: 17
Joined: Tue Jun 25, 2019 2:22 pm

Re: Note Updation - Person Preference is not updated properly

Post by kschutten » Mon Jul 15, 2019 4:06 pm

Dear mahadev & rkaruppusamy,

Just had a brainwave and it seems to work fine
Here follows the (maybe not so temporary) workaround (or is it intended behaviour?);

After the update, make 2 extra API calls:

To associate a new lead

Code: Select all

PUT .../entity/Note/{noteid}/leads/{leadid_new}?BhRestToken=...
To disassociate the old lead

Code: Select all

DELETE .../entity/Note/{noteid}/leads/{leadid_old}?BhRestToken=...
Good luck!

Post Reply