Quote Originally Posted by jsarwar View Post
Is it possible to use UPC field instead of model field to update products using easy populate. If yes what change we need to make in files?
Yes, though I didn't make it as easy as I thought I had...

Apparently a new notifier needs to be added in to allow further "development" to use an alternate field,..

There are two basic factors involved with details to be captured/handled in what appears to be two files:

admin/easypopulate_4.php : Need to populate 'EP4_DB_FILTER_KEY' with the key name to be used later in import... This is normally read from the database, but it could be pre-loaded in the file load structure or the database could be updated to include the extra option(s).
admin/easypopulate_4_import.php: sometime either within or after this section: switch (EP4_DB_FILTER_KEY) { ... } need to set each of the variables identified within that section to the desired state for your new primary key. I was thinking that a notifier was included to support this, but I don't see it... Obviously could add a set of code directly in that file's section to handle your specific case.

Considering that the UPC "mod" is recognized, there is no need to add an additional custom field to track for export/import, but if the new field was not a pre-recognized field then would need to add it to the list of fields to process.

Of course and has likely been described countless times in here, is there a reason that the UPC code isn't part of the model?