Given Eric's compilation below my proposal (stated initially as 2.5) almost becomes Option 5, with parts A and B. It is probably much too much work to implement but it would allow flexible control from OpenERP or Magento IMHO. I apologize for the length of the comment below.
5a: Link products from OpenERP to Magento that are here-to-for unmapped while having the same REFERENCE CODE and SKU. When an OpenERP Reference has several Magento items in different websites or servers are found, give the option to link to one or many of those items. A marker should be set for "mapped" so that ongoing questions are not asked (unless new matched items appear in Magento universe). 5b: Link products from Magento to OpenERP that are here to for unmapped having the same SKU and REFERENCE CODE. If not found (as now) create a New Product in OpenERP. If multiples are found (I don't understand why there would be multiples in OpenERP, but it seems multiple Magento Websites would create this) give the choice to map to the multiple items or to consolidate mapping to one (or at least fewer) items. Comment on above: In general I prefer the idea that OpenERP has Master Records that then have physical locations that are linked to web locations. One Physical location could link to one web locations, or to multiple web location based on preferences. Still there should generally be only ONE OpenERP Master Product per Company, and therefore only one SKU (REFERENCE CODE) - one Item (not multiple items with the same SKU). Multiple company setups MAY break that but better would be that they actually "share" the foundation definition rather than creating new duplicate REFERENCE CODE - SKUS also. This "exclusivity" of Reference Code could potentially be broken w/ separate companies with a "check box" allowance in setup. ASIDE Now: I feel that each PARTNER should have a CUSTNO that is exclusive to it and still controllable at setup time and in KEY CHANGE mode only. I feel the SAME should be for an ItemCode(REFERENCE CODE/SKU). Generally then Custno and ItemCode would be default linking objects between systems. I see the logic of linking to serialized numbers by default as is now, but the ability to Definitevely link to Customer Numbers and Item Codes aids in all sorts of linking objectives between systems so long as said Codes can be created in various systems. REFERENCE CODE gives this ability now in OPENERP. I have not found the field to control in PARTNERS however in OPENERP. I believe OpenERP took away the "Partner Code" in version 7 for some reason. Perhaps there is an extension to bring it back. I would find it helpful. Which ever way this goes it will work and it is generally working now. I am simply envisioning a Kettle type situation where various databases can find their perch and relationships in the Stew. Thanks for all your hard work Coding. I see great value in relating databases to each other and look for simple controls is all. best to all, Landis Arnold Boulder, CO ----- Original Message ----- From: "Eric Caudal" <eric.cau...@elico-corp.com> To: openerp-connector-community@lists.launchpad.net Sent: Thursday, April 24, 2014 7:54:37 AM Subject: Re: [Openerp-connector-community] Automatically link imported products on existing ones by SKU Option 4 or 3 (with setup) Eric CAUDAL Eric Caudal CEO -- Elico Corporation, Shanghai branch OpenERP Premium Certified Training Partner Cell: + 86 186 2136 1670 Office: + 86 21 6211 8017/27/37 Skype: elico.corp eric.cau...@elico-corp.com http://www.elico-corp.com On 04/24/2014 09:31 PM, Lorenzo Battistini wrote: On 04/24/2014 09:34 AM, Guewen Baconnier wrote: <blockquote> 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 Let me add an option: 4. Link products having the same SKU. When several are found, set the job 'failed'. Moreover, there could be a boolean field on the backend configuration saying 'Link products having the same SKU'. When disabled, all products are imported as new products. </blockquote> -- 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
