Column names from CSV are being wrongly considered to define the "key" not respecting the sensitive-case about rowy HOT 3 OPEN

Hey @harinij, mind if I take this up?

The field name conversion takes place here (i.e. from myURL to myUrl, for example).

However, I don't think removing the conversion (so the field key stays the same as the actual column name) is the right solution. The fact that the the field key is customizable by the user (when initially creating the column manually), means that no standard conversion (camelCase, or otherwise) -- or even no conversion at all -- is guaranteed to work in every case.

• One option is to remove the user's ability to manually change the field key when creating columns -- so the key would always be the column name in camelCase form. Then we can always obtain the field key using the same conversion.
• Another option is to allow the user to manually enter/change the field keys at the time of importing a CSV, as part of the import CSV wizard.

The latter option is obviously a lot more flexible and gives the users greater control. Please do let me know if I missed something.

from rowy.