Quote Originally Posted by wheat View Post
Other than starting with Model No -
1. are there other required fields (as in can I leave some out of the spreadsheet)
2. is there a "mandatory" order for the fields with information to be uploaded

Thank you for any help you may be able to offer.

P.S. we have successfully added the filed for UPC code but there are some others unique to most product lines we would like to include and a csv file with fewer columns would be much less cumberson

So, for the most part, this somewhat depends on which of the two currently supported versions you decide to download. The primary thread in github for this module has not yet been updated with the latest beta because there had been some issues identified with the changes that were made. The version referenced by the first post of this thread which is EP4 4.0.29 does require some additional fields to remain in place for certain items to be updated and it only supports using Model No. Version 4.0.32 (which in supporting another developer to add bookx product type management has required a few additional notifiers is to soon be updated to 4.0.33) is located by reviewing the last few pages of posts on this thread *should* allow updates for only the fields that are provided when imported and also now also supports the use of products_id and/or products_model, this aspect remains in review and if/when found to be otherwise functional please comment.

Another update to 4.0.33 is expected to help the store operator a little when entering the path to the file storage area. In times past, EP4 would accept storing a path from the store's base file location in the database, regardless of whether it was a path to the admin directory or somewhere else. Unfortunately for EP4, even ZC doesn't store information in the database about the admin directory path, so I saw it necessary to follow the same vein and to identify a way to not add the admin path to the database. At present though, the path could still be entered contrary to direction/request. So, I've found a way to "automatically" rework the indicators when EP4 is accessed but am looking to move that action up to the point of initial data entry instead.

There is absolutely no sequence necessary for the fields that are included other than I believe there should not be any missing field headers between columns... Haven't tried it, don't know what would happen. :) If you happen to have Stock By Attributes installed, I can say that there was some consideration into the sequence of the columns generated for upload to minimize the likelihood of an inadvertent change being made to the data that could cause a bad import, but sequence is still not required.

Now, all *that* said, if you have taken some time to read through the documentation or installed the application, you would have seen that there are some filenames that are "triggers" or do specific actions. For example a specials file causes different operation than a full product file. This has to do with the internal tables and ties between data and the tables. One thing that has made EP4 a bit of a powerhouse is that the queries and data are focused on the task rather than having large queries with lots of data. Your extra product table fields can be added and should be processed as discovered in the data file.