LISE doesn't import leading "0"

[smithdesign77]

Hello together,
today I found a funny behaviour and wondered if you could somehow help me to get that solved:
I wanted to update the entries (currently in development, so there are only very few entries) through Excel via the CSV export/import. I downloaded the file, found in one column (a custom text field) leading zeros (it's about drinks; here they have like '0,7 liters'), even so in Excel * - very nice, just as intended.
Saving the file from Excel as CSV also shows the correct field value (checked in a stupid notepad editor software) - however, as soon I upload the file and merge the data into my LISE instance, the values are being changed from '0,7 liters' to '7 liters' — so I assume this must happen on the CMS or respectively LISE part.

My configuration is the newest CMSms release 2.1.6 with the afaik newest LISE version 1.2.3. (I'll later attempt to run it on PHP7, yet the module manager keeps breaking as soon PHP7 is on, so for now it is PHP5.6, again afaik the latest release)

I hope these informations are sufficient - I don't get any errors, only the changed values here. I actually assume it is much more about the comma, but I'd really need that, if possible.
Thank you very much for your time, I appreciate your support while I have no clue how to figure this out.

* I assumed Excel would start messing up values like treating numbers for numbers and not text - therefore killing the leading zeros - but amazingly didn't.

[paulbaker]

Something somewhere in the chain is not understanding "0,7". The first thing I would try is a global change on your data:

Code: Select all

0,7 liters -> 0.7 liters

[Jo Morg]

LISE should import fine as long as the CSV file is properly formatted. I never had any issues with commas in fields so far...
Check the CSV files and see if there are any missing double quotes that may be responsible for that behavior.