openerp-connector-community team mailing list archive

[Sebastien Beau <sebastien.beau@xxxxxxxxxxxxxxx>]

Hi Guewen,
As said by David we finally develop the export before the import of
attributes as our customer have an empty Magento and all attribute will be
imported in OpenERP. So in our case exporting is more urgent then importing
(depend of the customer).
We keep the correct design for managing attributes (no use of _inherit) so
we will be able to map the attribute when we will develop the import.
I am not sure that we will have the time to implement the import on our R&D
time but It will be not hard to do as the model will be already here, so if
a customer is interested we (or you) can develop it.

The David work will only fill a part of the Blueprint and not the totality.

See you




2013/10/7 David Beal <david.beal@xxxxxxxxxxxxxxx>

> Hi Guewen,
>
>
> You're right, there is a difference between blueprint and our
> implementation. It's because in our customer project there 'll have a new
> magento with no data to import.
>
> In this case all datas will be managed in openerp. When a new project will
> require importation (akretion project or other contribution), we'll join
> all blueprint requirements.
>
>
> David BEAL
> www.akretion.com/fr
> intégration OpenERP <http://www.openerp.com/community>
> +33 (0)6 67 22 86 89
>
>
> 2013/10/7 Guewen Baconnier <guewen.baconnier@xxxxxxxxxxxxxx>
>
>> Hi,
>>
>> I just looked at the work in progress on the branch
>> https://code.launchpad.net/~**akretion-team/openerp-**
>> connector/connector-magento-**export-attributes<https://code.launchpad.net/~akretion-team/openerp-connector/connector-magento-export-attributes>
>>
>> Thanks for working on that David.
>>
>> If I understand correctly, the attributes can be created in OpenERP and
>> are pushed to Magento. However, most of the configuration of the attributes
>> still needs to be done on Magento (ll.117-153 of
>> https://bazaar.launchpad.net/~**akretion-team/openerp-**
>> connector/connector-magento-**export-attributes/revision/909<https://bazaar.launchpad.net/~akretion-team/openerp-connector/connector-magento-export-attributes/revision/909>
>> **).
>>
>> What's the point of such a feature? I don't see much the value of being
>> able to create an attribute from OpenERP if anyway I need to configure it
>> on Magento afterwards. Do I miss something?
>>
>> This is not what has been discussed (by me and Sébastien) and written on
>> the specifications blueprint here: https://blueprints.launchpad.**
>> net/openerp-connector/+spec/**product-attributes-**integration-magento<https://blueprints.launchpad.net/openerp-connector/+spec/product-attributes-integration-magento>where we stated that the most important thing was the ability to import
>> them from Magento and bind them easily with the OpenERP attributes, are you
>> going to implement this blueprint too?
>>
>> Thanks!
>>
>> --
>> 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/
>>
>
>