Hi all.
I’m refactoring a few tables and have run into an odd problem during the data import.
I exported a view from a very wide table. Then I created a new table to hold a subset of the original data. Finally, I tried to import the data into the new table.
Here’s the error I get:
All of the columns are lined up. The field types are compatible. (I think..) I don’t know where to go from here.
Mike
Hello,
I’m having similar issues.
I’ve successfully imported several databases into Excel without any problems.
But now, for some reason, it’s suddenly not working anymore.
The fields are created based on the descriptions, but no data is imported.
It doesn’t matter whether it’s Excel or CSV, self-hosted or in the cloud.
What’s striking is that when the fields are created automatically, field types other than the standard text field are suddenly assigned (which also don’t match the field’s content)—this hasn’t happened before.
If I reduce the number of fields to be imported, the import sometimes works. However, I can’t identify any specific field that might be causing the issue (especially since there are no unusual field types).
It seems to me that a really nasty bug snuck in with the latest NoCDB update. I would expect to see some information and feedback in the forum, even though there’s hardly any activity there.
Regards, Ulrich
@Ulrich - thanks for reporting this. field type auto-detection was un-intentionally enabled by default. we will rectify in our next release.
@Thud1415 can you share a sample file & steps to reproduce your issue?
