A recent enhancement with Bullhorn integrations has just been rolled out. What I’m referring to was the added “Divisions for Emailer” field to our field mapping area. This popped up from a question in Cazoomi’s customer support. See how it was resolved below.
A subscriber tried to find the field option “Divisions for Emailer” which is a Bullhorn standard field and is mainly used to segregate lists. And since SyncApps, by default, only syncs those built in available MailChimp fields for email address, first name and last name with all the other data fields which include the address, phone number, title or lead source need to be created as list fields (merge tags) in MailChimp for the specified “Master List” in the previous SyncApps configuration screen, means that this specific additional field can’t be mapped to MailChimp in just 1 field unless it is a text field.
If you wish to learn more about MailChimp merge tags, take a quick jump to http://kb.mailchimp.com/merge-tags/using/getting-started-with-merge-tags.
And with the Subscriber’s Sync Profile, SyncApps only retrieves “Secondary Owner” custom field being created using customText1. It can be checked in the Field Mappings menu in Bullhorn.
But as it turned out, “Divisions for Emailer” is a standard field in Bullhorn and is a Contact Field. Thus, it was quickly rolled it out in SyncApps for all subscribers.
Another topic was brought up and was about syncing tearsheets in Bullhorn. SyncApps normally tries to retrieve all records on any first sync initialization only, then subsequently syncs only retrieve and update records since the previous sync. SyncApps is going to be updated to stop after reaching 100 records on the trial, however, know that the API does not support retrieving candidates for specific tearsheets only. That said, the next sync should be a lot faster as it looks only at modified candidate records only.
For Contactor Lead Tearsheet, SyncApps only retrieve records on the selected Tearsheet because there is an API to accomplish it.
So basically, the subscriber chose to sync Candidates for the field “Divisions for Emailer” thus making the field unavailable.
Don’t hesitate to ping us at [email protected] whenever you hit any snags in your integration scenarios as you setup your Sync Profile.
