Originally Posted by
mc12345678
The message provided indicates that whatever is being used for your "unique record" is not present in the first line of the file... By default that field header is: v_products_model
By making changes in the configuration menu, it is possible to instead change to using: v_products_id
By way of code, there is an observer that can be used to select/use a completely different primary key.
Note that again, this "primary key" is what ties the data being imported to the record(s) in the database. Depending on what is used for the primary key, multiple database records may be affected. For example, if there was a word within the products description that was used as a "primary key", then every record that has that word would be impacted by importing a row of data with that word. This is why when using v_products_model if more than one product has that exact model designation that import of a record with that model designation will affect all such product.
As far as the reference to using/not using the prefix "v_", that is associated to identifying other product table fields that are to be used in the import/export. The place where the "v_" is omitted is within the configuration settings for the User Defined Products fields... When entering/adding such fields within the configuration menu, they should be added using whatever the field is actually called in the products table.
Perhaps the above helps? It may be of assistance to provide the configuration settings and other pertinent information to get to your solution.
Bookmarks