EasyPopulate 4.0 Support Thread

[mc12345678]

Okay, so please understand, if it is category destination that is the issue/concern, in the column: category_name_x, whatever you have there for each "instance" of the product is to which it will be tied.

If you want to have a product in main category Traditional Balls and sub-category Traditional Balinese Designs, then the category_name_x (sorry if I have the wrong field name at the moment) for the given product would need to be: Traditional Balls^Traditional Balinese Designs.

How you get there, that would/could depend on a number of things, but the important thing is that you can manipulate the data as much and however you would like to be able to end up with the store "arrangement" desired.

Basically, you have to assign/designate the category structure that you would like the/each product to have prior to uploading. Once uploaded, categories may get generated that are irrelevant or desired to be removed.

So, I'm not exactly sure (still?) what the confusion is or if it is just a matter that it takes "so much" to set it up the first time.

Ohh, yeah, so if you already have the product in the mega store where you want it and you don't want to add the product to any different categories, then simply delete the related category_name_x field(s) from the file being imported. That way, the product is not applied to any new category(ies) and is simply updated. Of course if taking data from the mega store to an individual store, want to be sure that the data fed to the "individual" store only applies to that store or at least is not carried over from something.

[shags38]

Okay, so please understand, if it is category destination that is the issue/concern, in the column: category_name_x, whatever you have there for each "instance" of the product is to which it will be tied.

If you want to have a product in main category Traditional Balls and sub-category Traditional Balinese Designs, then the category_name_x (sorry if I have the wrong field name at the moment) for the given product would need to be: Traditional Balls^Traditional Balinese Designs.

How you get there, that would/could depend on a number of things, but the important thing is that you can manipulate the data as much and however you would like to be able to end up with the store "arrangement" desired.

Basically, you have to assign/designate the category structure that you would like the/each product to have prior to uploading. Once uploaded, categories may get generated that are irrelevant or desired to be removed.

So, I'm not exactly sure (still?) what the confusion is or if it is just a matter that it takes "so much" to set it up the first time.

Ohh, yeah, so if you already have the product in the mega store where you want it and you don't want to add the product to any different categories, then simply delete the related category_name_x field(s) from the file being imported. That way, the product is not applied to any new category(ies) and is simply updated. Of course if taking data from the mega store to an individual store, want to be sure that the data fed to the "individual" store only applies to that store or at least is not carried over from something.

Thanks MC - seems from what you are saying I can manipulate the files prior to uploading - something I have not tried as yet so I will give that a shot.

cheers,
Mike

[mc12345678]

Thanks MC - seems from what you are saying I can manipulate the files prior to uploading - something I have not tried as yet so I will give that a shot.

cheers,
Mike

Absolutely!!!

That is one of the main concepts of use, the ability to manually modify the data in any desired way to target a final goal. Like, if one wanted to increase all product that meet a certain criteria by a particular amount, the data could be sorted and the price(s) so adjusted. Or product description could be revised, etc...

[solo_400]

I just want to give my compliments to the people behind this module and once again to the fantastic ZC community and those helped me to find what I needed.

[mc12345678]

I just want to give my compliments to the people behind this module and once again to the fantastic ZC community and those helped me to find what I needed.

It certainly is more than one person behind this software. Feedback and input has been the most helpful to make modifications/improvements. I think that's the way with any plugin out there.

Glad that it's working for you!

[lankeeyankee]

I think another configuration option that would be very useful is to limit the export to canonical or master product only, thus eliminating duplicate linked products in the file. Currently I have to manually do this following the tip from the open office forum. Thanks for making this great module even more useful than before, I love where this has been going.

[mc12345678]

I think another configuration option that would be very useful is to limit the export to canonical or master product only, thus eliminating duplicate linked products in the file. Currently I have to manually do this following the tip from the open office forum. Thanks for making this great module even more useful than before, I love where this has been going.

Take a look at my github master branch... Already ahead of ya'.. :) Had a few other things to fix before posting to the ZC forum (want to be able to reduce the columns that are needed when uploading attribute related files and possibly add a little direction about how to prevent changing attribute related columns to zero's instead of +'s or -'s... Something else too, I forget at the moment, but not yet ready to release as a package, but what is there works...)