Import error after updating to 4.0

[jnsgioia]

I use ~ as the multiple value separator in my csv import.  After I upgraded to 4.0 the features field did not populate and the import failed.  I downgraded to 3.0 and everything worked as normal.  I can not use ; as the multiple value separator.  How can I fix this?  Thank you.

Edited November 15, 2022 by jnsgioia

[wakabayashi]

I don't know exactly, what you are talking about. Do you mean 1.4 vs 1.3?

Can you provide the csv file? Do you get any specific error?

[jnsgioia]

Sorry I was unclear.  Yes, I meant 1.4 vs 1.3.  I have attched the file which failed in 1.4 and worked in 1.3.

Thank you for any help.

tblPrestashopUpload.csv

[wakabayashi]

@jnsgioia I have looked one hour into it. There is some issue, but it's not about the separator but about some character in your data. You use "¾". This seems to break in the new version.

@datakick My knowledge is not too good about special characters. I can imagine, that the fix or at least the understanding of the problem is much easier for you.

[datakick]

This is a regression. The root cause is that the code in 1.4.0 do not check if the input file needs to be converted to utf-8. We have to reintroduce this check.

Tracked here: https://github.com/thirtybees/thirtybees/issues/1549

Workaround: encode your csv files in UTF-8 instead of ISO-8859 encoding.

[datakick]

Fixed both in in main and in 1.4.x branch.

 

[jnsgioia]

I just updated to 1.4 again and tried to upload a csv file (file is attached).  It failed again.  This is the error that showed on the fail:

Errors occurred:

• Property FeatureValue->value is not valid
• Property FeatureValue->value is not valid
• Property FeatureValue->value is not valid
• Property FeatureValue->value is not valid
• Property FeatureValue->value is not valid

tblPrestashopUpload.csv

[datakick]

5 minutes ago, jnsgioia said:

just updated to 1.4 again and tried to upload a csv file (file is attached).

By 1.4 you mean bleeding edge, right? Because fixes are in the bleeding edge.

If you, by any chance, updated to 1.4.0 (stable release) again, you would get the same buggy version as before.

[jnsgioia]

1 minute ago, datakick said:

By 1.4 you mean bleeding edge, right? Because fixes are in the bleeding edge.

If you, by any chance, updated to 1.4.0 (stable release) again, you would get the same buggy version as before.

Oh, sorry, I will update to the bleeding edge version and try again

[jnsgioia]

Works like a charm now, thank you!!!

[datakick]

8 hours ago, jnsgioia said:

Works like a charm now, thank you!!!

Awesome, thanks for confirmation.