Asset upload from CSV including spaces?

[Peter Clough]

One of our asset management team has recently encountered an issue where the order number has an additional unprintable character at the end. When looking at the CSVs being used, and comparing them to older ones that have worked as expected, the CSVs also have what looks like a space at the end of the field. My colleague thought that the upload would normally abort if there was a space in that field.

I'm not aware of any recent changes, but is that understanding correct? My other theory is that the character renders as a space in a CSV, and the error diamond in Hornbill, and that there's an issue with the original CSV generation.

[Steve Giller]

15 minutes ago, Peter Clough said:

My colleague thought that the upload would normally abort if there was a space in that field.

h_order_number is a VARCHAR(32) - spaces (and special characters) are a valid character in this field, so if it's in the csv, it will upload.

I'd recommend two steps:

• Review the underlying data at source to see if the extra character is there.
• Try to avoid opening the CSV in Excel at any time - Microsoft applications will happily reformat and replace characters as they see fit for no apparent reason.

[Peter Clough]

This makes sense, thanks very much. Microsoft being Microsoft seems like it might be the most likely culprit.

[Steve Giller]

I also noted an internal comment that suggested the csv may be saved as UTF-16 where the import is using UTF-8.
I've not been able to test this, but something to watch for.