NUMERIC type ingestion for XLSX files (V6.1)

89 views
Skip to first unread message

Steven FEREY

unread,
Mar 15, 2024, 11:02:02 AM3/15/24
to Dataverse Users Community
Hello,

When ingesting an XLSX file we observe unwanted behavior: Currently a non-zero numeric value is ingested with a 'Double' java object in all cases.
With this logic, an integer is automatically converted to a decimal number.
This may be illogical in certain cases (phone number, street number, etc.) :
2 -> 2.0
-2 -> -2.0
2.5 -> 2.5

Is this behavior logical and expected ?

If this behavior is not intended, do you want us to create a workaround to propose an improvement to keep integer numbers during ingestion ?
2 -> 2
-2 -> -2
2.5 -> 2.5

Also, this ingestion logic is not present in the case of ingesting a csv file.
This behavior is observed in V5.12.1, V5.14 and V6.1 of Dataverse.

Thanks,
Steven.

Steven FEREY

unread,
Oct 3, 2025, 3:10:57 PM (11 days ago) Oct 3
to Dataverse Users Community

Hello,

I’m following up on the message below as the issue is still present in the latest release (Dataverse 6.8).

To verify, I created a test dataset available here:
https://demo.dataverse.org/dataset.xhtml?persistentId=doi:10.70122/FK2/T8QLXW

As a reminder: when ingesting an XLSX file, any non-zero numeric value is ingested as a Double Java object. This results in integers being automatically converted to decimals (e.g., 22.0), which can be problematic in certain contexts (e.g., phone numbers, street numbers). The behavior differs from CSV ingestion, where integers remain integers.

Could you confirm whether this behavior is intended? If not, would you like an issue to be created in the GitHub project?

Thank you for your time and feedback.

Best regards,
Steven

Message has been deleted

Philip Durbin

unread,
Oct 10, 2025, 11:41:54 AM (4 days ago) Oct 10
to dataverse...@googlegroups.com
Hi Steven,

Sorry for the slow response! I just confirmed this bug myself using the file we mention at https://guides.dataverse.org/en/6.8/user/tabulardataingest/excel.html#example-data

There's a "Units" column that looks like this:

Units
95
50
36

Dataverse converts them into this:

95.0
50.0
36.0

If you don't mind creating an issue, it would be appreciated!

Thanks,

Phil


--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/43a4d0aa-f3ec-4fb0-ba42-8a28b4497632n%40googlegroups.com.


--

Steven FEREY

unread,
Oct 13, 2025, 5:41:20 AM (yesterday) Oct 13
to Dataverse Users Community
Hello Philip,

Thanks for the feedback.
The github issue has been created here: https://github.com/IQSS/dataverse/issues/11894

Thanks,
Steven
Reply all
Reply to author
Forward
0 new messages