mc12345678:
The "important" part of the filename is everything up to and including the letters EP. Anything after that is up to you. (extension needs to be .csv)
The first part of the filename let's EP4 know what types of fields to expect so that it can process properly.
Don't recall the full feature availability of 4.0.28 with the current version being 4.0.36, but the process is basically logic based. The field list basically needs a single anchor point (primary key) and one column of data to be modified. Every row of data is attempted to be processed from top to bottom.
Your edited data file should look very similar in format to the original saved file if you were to look at each with a plain text editor. Be sure to follow the Open Office or Libre instructions to save as/export the file in UTF8 csv format.
Bolded text should answer the question about sequencing.
stringplayer:
Hi again
Thanks very much. I am now getting the hang of it. Just a few more questions.
How do I mark a product on the spreadsheet to delete before importing.
How do I mark a product status to off on the spreadsheet before importing.
If I rearrange the lines of the spreadsheet order of the products does it make any difference when importing (keeping the product on the original lines).
When putting a new product onto the spreadsheet is there anything that has to be done such as the index number etc or does it make its own when imported.
I think that will be it once I have these answers. Much appreciated.
May I suggest searching the readme.txt file for two different words: the first delete (identifies how to completely delete a product), the second disable (identifies how to disable a product though this also would be easier seen/understood if an export of the database was performed, a product disabled and the export again performed to see what changed and how.)
As adding a product, it still somewhat depends on whether you've upgraded or not, but the primary key (anchor field) basically determines what to do... the historical method of using EP was to use the model field. Each product to have its own model, no 2 products to have the same model. If two products have the same model, then when importing, they would both get updated which could/would cause some undesired issues depending on how much data (number of fields) was updated.
Now as far as deleting. Are you sure you really want to delete the product? Unless you are using the products_id as a primary key, then deleting the product followed by importing a new product (with the same information) will cause a new products_id to be created which is quite literally a new product even if it is called the same thing as before, weighs the same, is described the same, etc...