What’s strange is that I don’t have this Problem. Only the first time I copy paste a table into coda it changes the column type from Text to eg numbers. After that coda doesn’t change the column type. But what often occurs is that a certain column type appear different in formulas, which is quite confusing.
Well one workflow where this is really problematic is : we have a few empty tables that we use as “input” field where we pass some table data from sources that cant be imported any other way. We than use coda “import” button that transforms this data and perform various calculations etc, before “moving” it to “destination” table.
In this workflow its really, really annoying. That is example on top of the head.
But problem is that I dont see how this behaviour is benefical in any use case.
I assume after the “import” you move it manually to the destination table, and then the column types of this destination table change based on the pasted, imported data?
Actually No, we past data in “import” table (and thats when on 1/3 cases or even more Coda goes loco and star changing input fields that no one asked for) and than we setup button Import whioch when pressed does a quite a few required calculatons and transformation and send data to destination table while deleting everything from “input” table so it can be ready for next time.
BUT
Since Coda (for God knows what reason) likes to change field types that Maker has set (and knows better than Coda what he needs) those calculations can be affected and produce errors or even in worse case pass data to destination table that has no sense which in end affect reports and analysis we do. Its really frustrating.
This is just one use-case on top of my mind. Although I really cant see a use case where platform decides to change data type YOU set as maker on its own, its really not good feature. Imagine that happening in SQL, MongoDB or any bloody database…
Can somebody at Coda please implement a toggle to disable this horrible feature?!?
Just give us the option, PLEASE!