Spreadsheet doesn't import csv files correctly

Do you want to: Suggest a feature / Report a bug / Ask a how-to question
For feature suggestions, describe the result you would like to achieve in detail.
For bug reports, provide the steps to reproduce and if possible a minimal demo of the problem.
OS version: LinuxMint 22.3
App version: 9.2.1.43 (x64 flatpak)
Downloaded from: ONLYOFFICE website / Other (specify). Please point us to the installation guide that you used as well.
Additional information:
Any relevant details about the situation. You can also attach images and videofile to the post (or to place them to external storage).

The following does not import correctly into OnlyOffice as spreadsheet:
test;750000;75000.00;“750,000”;“750,000.00”

Neither does this:
test,750000,75000.00,“750,000”,“750,000.00”

Notice in both cases the fourth column in the spreadsheet will show 750.0,000 instead of 750,000.00

Hi @bobinmurphy,

Thanks for the report. We are currently analyzing this behavior.
We will get back to you here as soon as we have an update!

Depending on the numeric value found in the CSV record, the numeric data may be misinterpreted as a DATE when imported and assigned a DATE format as well.

Hi @bobinmurphy!

First, thank you for your patience while I looked into this.

I was able to reproduce the import issue you described on version 9.2.1.

The good news: I tested this on the upcoming version 9.3, and the issue is already resolved! You will be able to import this data correctly once the update is released.

Regarding the date misinterpretation, I wasn’t able to reproduce that part yet. Could you please provide more specific steps or the exact values that are converting to dates? I’d be happy to check that for you as well.

The issue with some numeric fields in CSV files being imported as DATEs was probably resolved in the 9.1 update. I was seeing it in the previous version but am unable to reproduce it after updating to 9.1.

Thanks for confirming that the issue with commas in numeric fields has been fixed in the upcoming release though.

2 Likes