ive been dealing with trying to solve this issue for the past hour only to be met with “column name or order mismatch”. and now ive finally tried to export the current database, and then import it on the same page, and it gave me the same error.
Same here.
Yup, started happening recently. It was working prior and now it’s just decided its done being nice
By the power invested by myself, I bump this report!
Edit: New Info
It seems that some column values work. and others dont. I had a column called “category”, when i changed it to “no_way”, it imported fine (along with 3 other columns, column desc example, before it)
When I changed the “no_way” column to “bro”, I get the error again 
I dont know if this helps at all since the error seems to be appearing inconsistently with no apparent pattern
This whole system will likely be rewritten in the future. Not sure exactly when.
1 Like
Its something i find myself using quite often though so soon (if possible) would be much appreciated 
Major “Breakthrough”
So, I recently discovered that the order database columns appear in blocks varies in comparison to the order you add them in your database. Using this minor detail, I rearranged my columns in my csv according to how they appeared in a basic create row block:
then i imported the data into my db, and to my little surprise, it actually worked
(this is how the columns appear in the database compared to the create row block)
I guess all this has something to do with the way columns are written backend? im not exactly sure, but im really happy ive found a work around for the time being until the system gets rewritten. Hope this helps anyone else