if i export the data, and then try to import the same file that was exported (by keeping only one column for a test and renaming some fields), I receive the same error.
Ok guys, I’ve found the problem. Moshe and the gang is aware of it as well, but here is what is happening…
mapping fields not in order from left to right is not supported in import. So, if I map column1, column4, column8, etc. it ignores that. It looks at the value for SKU (second attribute i define in mapping) while trying to store to “type” which is mapped to column 2
I’ll try and fix this myself and keep you all posted. It will be fixed in the next minor release, however, if you all are like me, you can’t wait
UPDATE ***SOLUTION***
Note: BE SURE TO CHECK THEM after they import!
I have now successfully imported my products, but here is how
- Make sure that the fields in your import file fall in the same order that the attributes you are mapping do in the Field Mapping List. You don’t have to map every attribute, just the ones you want. Then, make sure your import file fields fall in the same left-right order.
To ensure success, map the fields instead of using field names that are identical to the attributes. I haven’t tested this. You can if you want!
Also, make a test product that uses all the attributes you need and then export it. Use this as the basis for your field values. I was encoding things for the database, but the export showed a lot of text fields being used versus their integer value equivalents.
Somehow I manage to get it working, though.
Still I cannot create a custom profile, so I’ve used one of those default profiles embedded within Magento 1.0 (called “Import all products).
Now I can import items and images correctly, but the variable “store”, setted ad “admin” isn’t recognized yet and I have to edit each file manually after import in order to assign it to specific store.