There's a fundamental difference between how Legacy Import system treats CSV files and how the new PR8 system treats CSV files.
CSV is more than just a data set separated by commas, there's a protocol to follow (here's some basic info: http://en.wikipedia.org/wiki/Comma-separated_values) to make sure that you can have comma's in your text for example or use quotation marks properly without having any issues with your data.
In previous versions of our Import process we did NOT follow the protocol properly and as many previous threads have discussed (usually in the context of Excel adding extra quotes or other unwanted characters) there were workarounds for using Excel and getting it to play nicely in our Legacy system.
In the new PR8 Import system we properly follow the specifications of the CSV Protocol. Most importantly:
So if in previous versions you were using Notepad or some other mechanism to strip out the "weird" quotes that Excel adds, etc... you'll find that your old workaround will cause issues if you use the new Import system (you can still keep using the Legacy Import Systems without issue).
However it should be as simple as opening the file with any issues into Excel (or similar) and Save As CSV, this will properly format the data into the CSV spec and should work without issues in our PR8 Import system.
CSV is more than just a data set separated by commas, there's a protocol to follow (here's some basic info: http://en.wikipedia.org/wiki/Comma-separated_values) to make sure that you can have comma's in your text for example or use quotation marks properly without having any issues with your data.
In previous versions of our Import process we did NOT follow the protocol properly and as many previous threads have discussed (usually in the context of Excel adding extra quotes or other unwanted characters) there were workarounds for using Excel and getting it to play nicely in our Legacy system.
In the new PR8 Import system we properly follow the specifications of the CSV Protocol. Most importantly:
Fields that contain a special character (comma, newline, or double quote), must be enclosed in double quotes. If a line contains a single entry which is the empty string, it may be enclosed in double quotes. If a field's value contains a double quote character it is escaped by placing another double quote character next to it.
However it should be as simple as opening the file with any issues into Excel (or similar) and Save As CSV, this will properly format the data into the CSV spec and should work without issues in our PR8 Import system.
Comment