Totally Zenned
- Join Date:
- Jul 2012
- Posts:
- 16,908
- Plugin Contributions:
- 2
EasyPopulate 4.0 Support Thread
I think your question was clear, so I provided the requirements that must be met. How they are met is up to the updater.
So there is issue of making changes, making unintentional changes and there is the issue of potentially undesired addition of products.
Product is added when a model number is provided that doesn't already exist. (Don't change a model number, don't add a product with a new model number if no product is to be added.) Not exactly a product addition, but by changing a category/sub-category assigned to a product will provide a linked version of the product. Download of a linked product will look like there are two products with the same model number... Change of the first without change of the second (with both still in the upload file) will result in the product having the last version of the changed/non-changed data. See below.
A product is updated (whether any change is made or not) if a row exists with a model number that exists in the database. It also gets updated to the last row of data that has the same model number as one that already exists (don't duplicate model numbers in the store, won't update the model numbered product with the last row of data found.) Further, if a model number is blank after a model numbered product, then I thought that the previous model numbered product would get updated with that data. (Don't have a blank model number, but also see the previous about adding a model number.)
Then there is the minimum columns for which EP4 expects in order to update the desired column(s). Currently the code requires the product name column in order to process the product description. There are a few other similar minimum requirements, but those were not asked about nor would they impact the column(s) described as needing to be updated. So to update the description of a product, the products name must be one of the columns included.
So, of the few thousand products to be updated, all but the rows to be updated could be removed from the file being uploaded. Therefore the list of items to be touched would be reduced to just those to be edited. (Filter on the data by category, model number starting with, description contains, etc... And keep/remove the resulting rows placing them on some other sheet/csv file.)
Then as for column reduction/ease of editing, either all of the columns end up remainging "adjacent" to the original data, but visually separated during editing so as to minimize accidentally clicking in a field, or all columns except for the minimum to achieve the desired upload as required by the code are removed.
Regardless, it is not a download, change, update one field only one time and blindly upload process... There are some criteria that have to be met in order to meet the desired: no additions, no inadvertent changes, make the desired changes requirements...
If you have no linked products, all products have a model number and every model number is unique, no product quantities change between the download and reupload, and you only change the description field, then yes could download, open in open office, save in the format to be read, and upload the new file, then it could be that simple... (Hint, probably going to want to remove the quantity field/column in the upload file unless the inventory is also part of the upload update.)
On the issue of instructions, there are generic instructions in the wiki on using Easy Populate in general. None of those instructions get into the details of which columns must remain/can be deleted. It is not anticipated that such detailed instructions will exist (ZC periodically adds/modifies table field names, and this way it is not up to the instructions to pin-point a field, but how it interfaces with the store) and is why it is suggested to 1) try the desired changes on a test store to validate results especially when starting out with developing the process that works for a specific store, and 2) to backup the store's database before uploading/updating with EP4.