Hello,
I came across this strange issue that looks like a bug.
I import CSV files into my tables. Some file would not load with this error:
##########################################################
Can't analyze file. Please try to change encoding type. If that doesn't help, maybe the file is not: csv, or the file is empty.
##########################################################
All files are in UTF-8 encoding.
The "Table Data Import Wizard" throws the error message, then I close the error dialog box and the wizard still mapped the 5 first column headers from the CSV.
Eventually, I looked at the 6th column in my CSV file and realized that the header (top row in the CSV, e.g. field name) has a "special" character: ø
I removed it and the import was succesful.
I also have this character in other lines of the CSV (in the data) and that never was a problem.
The issue is only for the 1st line (column headers)
Is there something I could have done to avoid this?
This is a tiny problem, though. I now know how to avoid in the future.
Hope this helps.
I came across this strange issue that looks like a bug.
I import CSV files into my tables. Some file would not load with this error:
##########################################################
Can't analyze file. Please try to change encoding type. If that doesn't help, maybe the file is not: csv, or the file is empty.
##########################################################
All files are in UTF-8 encoding.
The "Table Data Import Wizard" throws the error message, then I close the error dialog box and the wizard still mapped the 5 first column headers from the CSV.
Eventually, I looked at the 6th column in my CSV file and realized that the header (top row in the CSV, e.g. field name) has a "special" character: ø
I removed it and the import was succesful.
I also have this character in other lines of the CSV (in the data) and that never was a problem.
The issue is only for the 1st line (column headers)
Is there something I could have done to avoid this?
This is a tiny problem, though. I now know how to avoid in the future.
Hope this helps.