v3.2.1

Bug Fixes

• Fixed the /getByExternalId feature to allow for all supported special characters (fix for known issue in v3.2.0)

• Removed limit for fields longer than 100k characters (#199)

v3.2.0

Features

• Added comments field to JobSubmission

• Faster loading of Notes

  Notes are now created with all associations in a single create call. This results in dramatically faster load times for Note CSVs.

• Faster loading when using exernalID for multiple files.

  Loading a CSV that depends on a previously loaded CSV, for example, loading a Candidate.csv then loading a CandidateWorkHistory.csv that references previously loaded candidates by externalID will normally use the lucene index based /search call to lookup the candidate's internal ID for creating the association. If the current user specified in the properties file has the User Action Entitlement: SI Dataloader Administration, then DataLoader will use a brand new /getByExternalID call to pull the internal ID without having to wait for the index to be ready.

Bug Fixes

• Fixed the size of the leadSource field to match the database (#145)

• Allow empty date cells (#177).

  Instead of rejecting empty date cells, DataLoader will do nothing. The date field for a row is not modified if left empty.

Dependencies

• Upgraded from SDK-REST version 1.2.8 to 1.2.11

Known Issues

• The fast lookup by externalID is currently limited in the type of externalID formatting that is allowed. The externalID is limited to no special characters, spaces or dashes. A warning will be shown, and the row will default back to using a regular /search call instead. This is a known issue, and is being worked for an upcoming release.

• A new test was added to show all possible special characters that DataLoader supports in search and query calls, which are used for looking up non-id association fields or an exist field. For search calls, see the Candidate example file: https://github.com/bullhorn/dataloader/blob/master/src/test/resources/integrationTest/specialCharacters/Candidate.csv. For query calls, see the Appointment example file: https://github.com/bullhorn/dataloader/blob/master/src/test/resources/integrationTest/specialCharacters/Appointment.csv. Most entities are search entities, and most entity fields are pre-parsed where most special characters are converted to spaces. So, while the DataLoader encodes all search values, if you are attempting to use a pre-parsed string field like customText1 for entity lookup, then those IDs should not contain special characters, as they will be pre-parsed by Lucene and will not be able to perform an exact lookup. ExternalID is a non-parsed string field. Non-string fields are always non-parsed.

v3.1.4

Bug Fixes

• Turned off the switch that limited max length of fields in CSVs to 100k
• Fixed issue where null IDs during loading of Custom Objects were corrupting results output file

v3.1.3

Bug Fixes

• Fixed a bug that prevented fileContent from being updated
• Added missing case for CorporateUser as a Note reference
• Fixed a bug where deleting a custom object required the parent's internal ID. Custom objects can now be deleted using any field from the parent that is configured, which allows for a seamless deletion experience when using results files as input to the delete command.
• Updated version of Apache Tika to take advantage of bug fixes in the offline resume parser (Convert File Attachments)
• Updated example files and properties files to better explain loading of custom objects.

v3.1.2

Enhancements

• Updated to use new version of sdk-rest
  • Allows for updating JobOrder and Opportunity dateAdded and dateLastModified fields (once the backend REST changes are rolled out everywhere)
  • Adds support for Candidate and Placement Certificates
  • Adds reportToPerson field to CorporateUser

v3.1.1

Enhancements

• Faster Load Times
  • Updated allowable number of threads to 15
  • Updated dataloader.preferences file with direct URLs for UK and West swimlanes for faster connections

v3.1.0

Enhancements

• When deleting a JobSubmission (soft-delete), then DataLoader will also delete any JobSubmissionHistory records that exist for that JobSubmission as well (hard-delete).

• When loading ClientCorporations, if an externalID is set for a newly created ClientCorporation, then the defaultContact associated with that corporation will have it's externalID set to the same externalID, but prepended with the word: defaultContact.

v3.0.2

Performance Improvements

• Using one call to associate multiple records instead of using individual associate calls. #142

v3.0.1

Bug Fixes

• Fixed bug where the countryID field was expecting countryName. Now, if using address.countryID, or address.countryName, the name or ID will work for either.

v3.0.0

Enhancements

• Added externalID to notes
• Enhanced error messaging when working with files
• Ability to edit or delete notes using ID or externalID
• Ability to update a value to blank/null

Bug Fixes

• Fixed bug where Notes were not able to be updated, only inserted
• Removed limitation of 20 To-Many associations