EasyPopulate 4.0 Support Thread

[Blenderite]

But when I imported the file into OO, there was no data in that column for the items already there. Can I delete that column and not have an error?

[mc12345678]

But when I imported the file, there was no data in that column for the items already there. Can I delete that column and not have an error?

For the moment no. EP4 works off of the model field, expecting every product to have a unique model. There are ways to autopopulate the database with a unique model number so that upon export, a model number would be present, the data modified then the import would make the change.

If there are/were no model # information in the initial export, then could do the following:

In the ZC admin-> tools->install SQL Patches box:

Update products set products_model = products_id;

Could concat() information to make it ever more unique or could only update values where products_model = '' or IS NULL, etc...

[Blenderite]

That worked great! Thanks!

[mc12345678]

That worked great! Thanks!

Glad that worked, just remember now though how the software works as currently written. All product to have a model number, if the model number in one row of data is the same as another, then the later row wll "replace" the content of the previous. The model # can be anything desired that fits within the model field. Also verify on your site side that you are okay with the current results of having a model # flled in the way it is...

[Blenderite]

Ok. Now, if I want to update a item, do I just use the same model number to update a particular field or what?

[mc12345678]

Ok. Now, if I want to update a item, do I just use the same model number to update a particular field or what?

When uploading/importing, yes basically, model number identified will be updated with the contents of the field header along the top. If you're doing a onsey, twosey type update, just include those rows in your upload file.

The best thing to do though is basically go through the readme, export the file(s) for the type of action desired, and when trying something "new", use a single row first. This program modifies the database, so it is always suggested to backup (use of a development site to try new processes is also suggested). There are a few different backup tools available in the plugins section. DrBytes' database backup utility is pretty useful.

[Blenderite]

That makes sense! Thanks!!

[fabburl]

Having a problem that I am uploading attributes with the basic attributes uploader following the template given by easy populate

I get the following message

Updated records: 2229
New Imported records: 0
Errors Detected: 0
Warnings Detected: 0

however, these are actually all new imported records?? I am not sure why this is happening or what I am doing wrong.

[mc12345678]

Having a problem that I am uploading attributes with the basic attributes uploader following the template given by easy populate

I get the following message

Updated records: 2229
New Imported records: 0
Errors Detected: 0
Warnings Detected: 0

however, these are actually all new imported records?? I am not sure why this is happening or what I am doing wrong.

Well, the reason for the above result is because the following sql when executed/queried provided a non-zero number of returned rows and as a result an update was performed:

"SELECT * FROM "
                        .TABLE_PRODUCTS_ATTRIBUTES. "
                        WHERE 
                        products_id = '".$v_products_id."' AND
                        options_id = '".$v_products_options_id."' AND
                        options_values_id = '".$a_products_options_values_id."'"

Each of the variables are collected by related queries above the condition.

This is of course assuming that the filename follows the convention of beginning with

attrib-basic-ep

Otherwise, the result is because the records were being updated as a full import or some other import style...

[fabburl]

Ah, I did not know the filename has to start with attrib-basic-ep - I assumed any name was fine. I will try again with that name then.