My Vote is 2.5 If several found, give a choice in the Connector Review Panels as to which one (or many) to link to.
I suppose the question has to do with one of direction. There should not be multiples in any specific Magento Instance, however ideally there could be multiple Magento Servers which would share SKU's. On the OpenERP side there could be One SKU and multiple locations, or simply One SKU which controls the multiple Magento instances. I feel there should be an aversion to more than One OpenERP item per SKU but there should be the allowance for multiple location inventories. So re direction. A new in OPENERP should be should be mappable to one or many different Magento Website Skus, and potentially many Magento Servers. The assumption should be linking the SKU. If a custom unlinking of SKU takes place there should be some specific controls on such. If a New Item is created in Magento and it finds a OpenERP Item with the Same SKU it should automatically Map there. In case of misuse, or mapping to another item the Connector Review Panel should force a confirmation of "multiple links". Ideally there would be a Connector Review of most all instances, as by default, there is, but I feel these subjects should go in front of simple item review (bring the magento mappings up first). I will read everyone elses comments now. Just read Guewen's request for input. Landis Landis Arnold Boulder, CO USA ----- Original Message ----- From: "Guewen Baconnier" <guewen.baconn...@camptocamp.com> To: "openerp-connector-community" <openerp-connector-community@lists.launchpad.net> Sent: Thursday, April 24, 2014 1:34:17 AM Subject: [Openerp-connector-community] Automatically link imported products on existing ones by SKU Hi, Following the question of [0] Jos De Graeve on the mapping of products, I propose a vote. The question is: should the core Magento Connector automatically link new imported products on existing products having the same sku-default_code. The arguments we had in a first place were that the default_code is not unique in OpenERP, so the link on an existing product would not be deterministic or would be arbitrary in case of multiple products with same sku. On the other hand, I think that most of the users expect to have this behavior. And the users not wanting it could still void the mapping with a custom mapper. The options: 1. Keep the current behavior: all products are imported as new products 2. Link products having the same SKU, when several are found, take the first found 3. Link products having the same SKU, when several are found, do not try to guess and create a new product [0] https://lists.launchpad.net/openerp-connector-community/msg00329.html -- Guewen Baconnier Business Solutions Software Developer Camptocamp SA PSE A, CH-1015 Lausanne Phone: +41 21 619 10 39 Office: +41 21 619 10 10 http://www.camptocamp.com/ -- Mailing list: https://launchpad.net/~openerp-connector-community Post to : openerp-connector-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-connector-community More help : https://help.launchpad.net/ListHelp -- Landis Arnold larn...@nomadic.net office: 303-444-2336 ext 11 cell : 303-601-0622 -- Mailing list: https://launchpad.net/~openerp-connector-community Post to : openerp-connector-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-connector-community More help : https://help.launchpad.net/ListHelp
