Missing Transaction IDs

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

Moderators: StaffingSupport, s.emmons, BullhornSupport

Kazemi
User
Posts: 33
Joined: Tue Oct 11, 2016 1:26 pm

Missing Transaction IDs

Postby Kazemi » Wed May 03, 2017 5:56 pm

As part of the event subscriptions API, we can retrieve `eventMetadata`. Typically this is an object with a bunch of different IDs. We're wondering about `TRANSACTION_ID` in particular. `TRANSACTION_ID` is useful for tracking the event across multiple subscriptions, since it's related to the change itself. But, it isn't always included in `eventMetadata`! We've been unable to spot a pattern - INSERTs, UPDATEs, and DELETEs all only sometimes include transaction IDs in "eventMetadata".

Why is `TRANSACTION_ID` sometimes not included in the response?

ColinC
User
Posts: 49
Joined: Fri Apr 08, 2016 4:54 pm

Re: Missing Transaction IDs

Postby ColinC » Tue May 09, 2017 9:39 am

Hi Kazemi,

Sorry I didn't catch this post sooner.

We have an active internal ticket now that is about records not generating transaction ids depending on workflows.

1. Update/UpdEntities.cfm (Entity > Activity > Internal Submission > Drop Down)
2. JobPosting/Update/UpdJobResponsesStatus.cfm (Entity > Activity > Web Response > Move to Internal Submission)
3. Update/AddJobResponses_platinum.cfm (Candidate > Add new submission > Add to job where submission already exists. This is tracked as an UPDATED event)

These do not generate transaction IDs at this time. Typically REST calls generate transaction IDs and a few places in app that aren't based in rest when specifically told to create the transaction IDs. However, this is not currently universal.
Colin Coffman
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)


Return to “REST API”

Who is online

Users browsing this forum: No registered users and 2 guests

cron