Hi, I’m encountering errors when trying to import numerical data into a table column which is set to “%” formatting.
An example: if the CSV row has a value in that specific column of 0.96 (ie. 96%), and I run the import to a table column that is already formatted as %, the value appears in the coda table as 0.0096. The import appears to process the underlying data as 0.96% rather than 0.96.
Is this a known bug?
Hi Rahul, I think it is less of a bug than an ETL mapping issue.
P
I’ve experienced the exact same thing @Rahul_Patel and I was very surprised to see it. Coda support said it’s not a bug, because they expect inputs in percent columns to be how it visually shows up: input 96 and that means 96%, input 0.96 and it means 0.96%. But I was surprised that the CSV import process is literally changing the actual value upon import. I disagree with how they set this up and I think they should fix it.
100% with you - cannot think of another application that handles it like this. Just means additional checks and error-handling, which is not ideal.
What’s the best way of escalating / voting for this to be looked at?