Skip to content

v3.2.0
Compare
Choose a tag to compare
@ndickerson ndickerson released this 12 Jul 17:45
· 329 commits to master since this release
v3.2.0
b703415

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.

Assets 4
Loading