I have a catalog system with files like 2016.01.jpg - I tried using 2016.01 in my CSV data to identify the asset and it quietly failed. No error, just no changes made (even to the other fields in the import).
I tried 2016-01 instead (and changed the file name accordingly) and it didn't work.
It worked perfectly when I changed the file name to 201601.jpg and used 201601 in the CSV.
I really would like to keep the decimal point in my file name because it exactly relates to my catalog system. I understand that might be problematic, so even the hyphen would work better than nothing.
It seems like any punctuation in the file name breaks the import, without notifying or importing any other fields.
I have a catalog system with files like 2016.01.jpg - I tried using
2016.01
in my CSV data to identify the asset and it quietly failed. No error, just no changes made (even to the other fields in the import).I tried
2016-01
instead (and changed the file name accordingly) and it didn't work.It worked perfectly when I changed the file name to 201601.jpg and used
201601
in the CSV.I really would like to keep the decimal point in my file name because it exactly relates to my catalog system. I understand that might be problematic, so even the hyphen would work better than nothing.
It seems like any punctuation in the file name breaks the import, without notifying or importing any other fields.