Quote Originally Posted by amandavz View Post
Okay...So I added a zip file to a product in the store, downloaded the detailed csv file, added a couple of more products with the same format that was on the spreadsheet, saved it, uploaded it into the Easy Populate and clicked the Import link and got this for an errors:

Located at the top of the page:
File Import Completed with issues.

Located at the bottom of the page:
SKIPPED! - Attribute Entry on Model: 2 - Not Found!
SKIPPED! - Attribute Entry on Model: 3 - Not Found!

It's telling me there were 2 errors detected but generated no TXT file with them...

I do appreciate your thorough explanation of how this works and I understand what you are saying. I appreciate it because if I can get this figured out this will be a very useful tool moving forward for future installs. :)

Did you do a basic attribute add to the two new products before downloading the detailed attributes? (Or within ZC add the attributes to the product without assigning all of the detail at the bottom).

Here is how I see the process generally running though I haven't gone back to confirm this exact sequence (and I think I provided something similar several pages back).
add a basic product, add a basic attribute to the product, add detailed product data, add detailed attributes for the product.

Basically, saying that basic data should be added before detailed data. Once a product is fully loaded in, changes can be made using the detailed data.

From the description above, I don't see that the attributes were captured to the product fully. The detailed attributes file includes specific data that is in the database after a basic attribute upload. (the id number). While it could have been programmed with less steps (looking up the attribute_id based on the name of the attribute), the overall flow is upload a basic file, download the detailed, make a change, upload the detailed. If want more options/data tied to the product, upload a new basic, download detailed, mod detailed, upload detailed...

The lack of the error file means that the code ran fine, but the data it looked for was not present... The error file is created on an actual error in the programming/SQL statement.

Make sense?