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., 2 → 2.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
--
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.