Trim pipe separated import fields on CSV import
|Target version:||Release 2.5.0|
|Google Code Legacy ID:||Tested version:|
When performing a CSV Information Object import, extra embedded whitespace in the pipe separated event creators list are not trimmed.
<space>S. Smith<space>|<space>T. Anderson<space
These names will be imported, and actors will be create with the leading and trailing whitespace intact. This will result in a new actor getting created even if actor 'S. Smith' (without spaces) already exists.
All pipe separated fields should be checked for this problem.
#1 Updated by Steve Breker about 4 years ago
This change trims all pipe separated elements contained in an import
CSV file. This was not occurring previously and extra leading and
trailing spaces were appearing in the import, and in some cases,
preventing correct matching when match is based off these fields.
Additionally I have added code to ensure culture and other fields are
trimmed. If these fields has leading or trailing spaces in the csv, they
where previously not being trimmed, and the term lookups would fail.
Custom column handlers had a similar issue and require trimming of
values to ensure leading and trailing spaces in the csv field do not
affect the import.