ECI Data Import Encoding
Yesterday I realised that my own manually typed csv file, used for testing, was not being imported properly. All columns of data imported apart from the PRICE column which contained a currency symbol. No errors are generated, MySQL and PHP simply leave the field blank. I’ve never come across this issue because normally a currency symbol will exist as it’s html equivalent, but when I manually typed my csv file I done what comes more natural.
To import data like that explain I had to add an encoding option to the Import Data form. Selecting UTF Standard allowed the data to be imported with success. This encoding option is also saved to the csv profile and it is assumed that it should be used for automated updating procedures also. The saved setting has no effect on Post Creation, encoding for that is handled by seperate options and more options will become available to apply encoding per campaign rather than global options on the Settings page.
Update
I’ve just realised that when creating posts using the Create Test Post button, I was getting an indication from the event statistics that the test was failing. This does not appear to be happening now so I think it must have been to do with the issue mentioned above. The null value in the PRICE column must have been due to what is really an error, one I never seen. There is a chance that it would have prevented the post being finished but I never went that far after finding the problem.
Anyway the solution is found so if you experiance this issue please upgrade to version 2.9 once it is released. I’m guessing no one will have the issue because most people use data that is generated in a way that is suitable for importing without encoding unless it is none English etc.