I am exporting a table from Excel in CSV (UTF-8) format with values for latitude and longitude using periods and six to eight decimal places. After importing into Bubble, the numbers are cut off after the second decimal. The corresponding fields in the database are of type “number.” Previously, I had set the fields to type “text,” which preserved the precision but caused other issues. Is there a limit to two decimal places during the import process?
Are you sure?
I am positive. I opened the exported CSV file in Notepad and the numbers are complete with a period and all decimals. Only after importing, they are cut down to just two decimals.
What makes you think that?
Share a screenshot of that actual data (not the overall DataView - Bubble always truncates numbers to 2 decimal places there - but that actual data as stored in the database).
I just ran mom own test and number are always correctly imported.
When I edit the record, the numbers show with all decimals, but the calculation (Haversine) is based on just two decimals.
As I said, that’s not the actual data - that’s just how it’s shown in the data view tab (all numbers are truncated to 2 decimal places the for display purposes on the data view tab).
But the actual data will be whatever it was on the imported CSV (unless it’s been changed by some workflow).
Thanks again! I’ll definitely look into this further. The issue became noticeable when I changed the field type from text to number—suddenly, the Haversine distance calculations became less accurate. That’s when I spotted the values being cut off after two decimal places. For now, I’ve reverted back to using the text field type, which restores accuracy, although it’s not ideal. Really appreciate your help!
I don’t understand…
What is the I issue?
(and. you should use Number not Text for this).