DupliKit options
Last updated
Was this helpful?
Last updated
Was this helpful?
Each of the DupliKit options are detailed below. Any changes to these values will only have an effect if the 'Save' button (appears at the bottom after an edit) is pressed and DupliKit is resynced.
The Overnight sync setting should generally be left switched on. This allows DupliKit to perform a sync automatically at midnight UTC. Having this option turned on will not impact a manual sync, which can still be performed at any time.
Having Dry Run turned on means you can perform the merge process without altering data in Bullhorn. Dry Run is a safety measure to ensure no updates will affect the live Bullhorn database. The dry run feature is turned on as a default when the product is handed over to you. When you are ready to begin merging records in Bullhorn turn Dry run off. Once dry run is switched off all merges will update the live Bullhorn database.
This is the pause time in between record merges in Bullhorn. This is initially set by Kyloe during the DupliKit setup. This pause time allows any other Bullhorn automation to complete between each merge. You should only edit this value after checking with the Kyloe Support team.
You can enter an email address here to receive a notification when a sync is completed. We recommend leaving this field blank as it will send a notification after ech merge.
These three sections affect the duplicate matching process in similar ways. Although split into three, some of the fields work identically across the different entities. Those that are unique are addressed separately.
The Custom query option function in the same fashion for all 3 entities.
By default, deleted and archived records are excluded from the DupliKit matching process. You can add additional restrictions here to exclude records that should not be considered by DupliKit.
For example, you may have a large batch of records that have been recently imported from another system. These have yet to be reviewed so should not be included in any matching process. You can then use a custom query to exclude these records.
We advise contacting Kyloe Support to discuss what custom terms you are looking to use so that we can provide you with the appropriate syntax.
By default, the field-level merge settings are set to 'ON'.
Some important points to note:
If any of these settings are switched on, DupliKit will identify a second master record. The secondary master is identified as the record with the latest datelastModified.
If any field on the main master record is blank but a value exists on the secondary master record then the value will be copied across into the master record field.
Only full addresses will be copied to the main master record. This means that if any field in an address is completed on the master record then the address from the secondary master record will not be copied to the master. This is to prevent creating one incorrect address from two different addresses.
If switched OFF when merging, DupliKit will move all related records from the duplicates to the master and no field data will be changed.
If the tearsheet merge setting is enabled then the master record will be included on all tearsheets that any merged duplicates were part of.
This setting is either on or off for both candidate and contact. It is not possible to enable this for just candidate, or vice-versa.
If the custom object merge setting is enabled then the master record will inherit the custom objects of any merged duplicates.
This setting is either on or off for both candidate and contact. It is not possible to enable this for just candidate, or vice-versa.
Skills and categories for candidates are automatically merged by DupliKit. If you would like to merge Skills and categories for client contacts then the 'Merge Skills and categories for Client Contacts?'' option should be set to 'On'.
The 'Client Corporation Locations merge' option is by default set as 'OFF'. If the 'Client Corporation Locations merge' option is switched 'ON' DupliKit will merge any duplicate company record's locations into the master record's locations.
If the Company Locations merge option is set to 'ON' then the following message will appear to make you aware that if DupliKit merges company records with locations reverting the merge will not restore the location information:
The merging of locations is an irreversible action. The reverted duplicate ClientCorporation will appear to have no Locations in Bullhorn, and the reverted duplicate ClientCorporation will still show the copied Locations.
Due to how Bullhorn manages Locations, it is not possible to re-link (move) Locations between Company records. Instead, DupliKit will create new Locations on the master Company. These new Locations will be based on the latest version of the Locations on the duplicate Company record.
If a Vacancy (JobOrder) was associated with a Location on the duplicate Company, it will be associated with the matching new Location on the master Company.
Due to the inability to move Locations via Bullhorn, it is impossible to revert these changes. This is why the merging of locations is an irreversible action.
Words to ignore from company names: Kyloe has added words here to allow more flexible matching on Company records. You can add additional words if needed. Within the Field weights' Company weights a value for 'Clean Name' is usually set. This identifies duplicates by removing the words listed under 'Words to ignore from company names' from all company names before testing for a match.
Any change to this list will not be reflected until the next sync is completed. If you wish to see this change immediately click the resync button for companies on the DupliKit dashboard.
All content in this field should be in lower case for the words to be excluded. It’s important to note that the clean name function only considers something to be a word if it is separated from another bit of text by a space.
The Worksite fields relate to any worksites that have been created against company records. In most cases these fields will be blank and can be ignored. If worksites are used, then these fields will be populated by Kyloe during the implementation of Kyloe DataTools. You should speak to Kyloe before making changes to these fields.
