Quote Originally Posted by scottj View Post
Thanks for the reply. The user defined field I added was v_map_enabled (I had a good chuckle... would've been funny had I added "field1") and the new MAP field *is* located in the products table. As I noted, I know just enough to be dangerous having modded the old EP1.2.5.4 for the MAP field. The contents of MAP_UL.csv test file was simply:

v_products_model | v_map_enabled
806-1206 | 1

As for the file name, this may be the most promising. I don't quite understand all that. I previously attempted to add about 100 new products using the Full-EPxxxx prefix and for whatever reason it deleted all the title/descriptions for the existing 10,000 products. Luckily I had a backup but understandably I've stayed far away from that prefix!

Without any mods I successfully upload metatag data using a CSV file called metatags_UL.csv (which is why I originally added EP4.0 since the old EP doesn't support metatag stuff). Thus I made the assumption, perhaps erroneously, that any file name will work if you just want to upload product fields without "triggering" any of the EP4.0 logic... logic which I readily admit I don't understand. References to it in the instructions were a bit ambiguous for me.

Thoughts?
So to confirm, your database has a field name that begins with a v_? Or if you were to look in mySQLadmin would it be map_enabled?

The code automatically adds v_ as part of creating the CSV file.

So, it looks like the only way to get those fields out of ZC is to do a full export. To get them back in, it looks like you don't have to do a full import. At least there is some data loaded without that type of file...

But I think the real problem is that you have already prefixed the field with v_...