openerp-connector-community team mailing list archive

[sebastien beau akretion <sebastien.beau@xxxxxxxxxxxxxxx>]

Ok got it, they is a big misunderstanding!

The "MAGENTO_HELP" was just here to said that if you don't know what this
option mean than => "look at the Magento Documentation". But you can
totally create a attributes from OpenERP to magento without any
configuration on Magento Side. You just need to link the attributes with
the group (missing part but hard do to synchronize correctly without
lossing flexibility)

I propose to remane the help message by "This fields is a magento specific
field, look at the Magento Documentation to know more about it" or
something else? what will be the best Message?
Note that Magento have not "tool tip" on the fields so it's not possible to
copy/paste the help message from Magento. The other solution will to take
time to find a good help message for every field.

See you


2013/10/7 Guewen Baconnier <guewen.baconnier@xxxxxxxxxxxxxx>

> On 10/07/2013 11:59 AM, Sebastien Beau wrote:
>
>> Hi Guewen,
>> I understand your point of view but for me exporting attribute is a
>> needed feature.
>>
> Yes, that's the point 2. in my email, that we excluded because it seemed
> complex to implement in first sight. But if you can afford to implement it
> properly, that's fine for me.
>
>
>  I see two existing case that need to export the attributes from OpenERP
>> to Magento.
>>
>> Migration from an existing system (os-commerce, or custom one)
>> ------------------------------**------------------------------**
>> ------------------------------**----------
>> Indeed when a customer migration from an existing system to Magento, in
>> many case he already have the concept of attributes in his system. So
>> the customer want to migrate it. Importing data into OpenERP is easier
>> than importing into Magento so I really prefers to import it in OpenERP.
>> Last year I did a project and my customer have something like 800
>> attributs, he paid a company for importing it in Magento and at the end,
>> he decide to do it manually because the import was too buggy, so I
>> prefers to be able to propose a solution directly from OpenERP
>>
>> Launching a new Magento Website
>> ------------------------------**------------------------------**-
>> You already have a Magento with 1000 attribut and want to create a new
>> one, exporting the attribut directly in Magento will save you a lot of
>> time
>>
>>
> I'm aware of that and I agree. This is covered by the point 2. of my
> previous email.
>
>
>> So for me it's usefull. But I agree with you, you will need to go in
>> Magento for adding the attribute in the group (depending of the customer
>> we may can in some case to directly export the group in Magento but this
>> mean that the group are the same in every magento!)
>>
>> "You may think I'm too picky or not enough pragmatic" => I think your
>> totally right and I always like your feedback, and you really did/do a
>> good job with the connector framework
>>
>> So I agree with you the feature will be uncomplete because we can not
>> manage the group correctly. Indeed managing different group, attribute
>> order for different Magento backend is not possible without adding a
>> restriction (all backend will have the same structure).
>>
>
> I fear that we have a misunderstanding. I was not talking about the group:
>
> +        'scope': fields.selection(
> +            [('store', 'store'), ('website', 'website'), ('global',
> 'global')],
> +            'Scope',
> +            required=True,
> +            help=MAGENTO_HELP),
> +        'apply_to': fields.selection([
> +                ('simple', 'simple'),
> +            ],
> +            'Apply to',
> +            required=True,
> +            help=MAGENTO_HELP),
> +        'frontend_input': fields.function(_frontend_**input,
> +            method=True,
> +            string='Frontend input',
> +            type='char',
> +            store=False,
> +            help="This field depends on OpenERP attribute 'type' field "
> +                "but used on Magento"),
> +        'frontend_label':fields.char('**Label', required=True, size=100,
> +            help=MAGENTO_HELP),
> +        'position':fields.integer('**Position', help=MAGENTO_HELP),
> +        'group_id': fields.integer('Group', help=MAGENTO_HELP) ,
> +        'default_value': fields.char(
> +            'Default Value',
> +            size=10,
> +            help=MAGENTO_HELP),
> +        'note':fields.char('Note', size=200,
> +            help=MAGENTO_HELP),
> +        'entity_type_id':fields.**integer('Entity Type',
> +            help=MAGENTO_HELP),
> +        # boolean fields
> +        'is_visible_in_advanced_**search':fields.boolean(
> +            'Visible in advanced search?', help=MAGENTO_HELP),
> +        'is_visible':fields.boolean('**Visible?', help=MAGENTO_HELP),
> +        'is_visible_on_front':fields.**boolean('Visible (front)?',
> +            help=MAGENTO_HELP),
> +        'is_html_allowed_on_front':**fields.boolean('Html (front)?',
> +            help=MAGENTO_HELP),
> +        'is_wysiwyg_enabled':fields.**boolean('Wysiwyg enabled?',
> +            help=MAGENTO_HELP),
> +        'is_global':fields.boolean('**Global?', help=MAGENTO_HELP),
> +        'is_unique':fields.boolean('**Unique?', help=MAGENTO_HELP),
> +        'is_required':fields.boolean('**Required?', help=MAGENTO_HELP),
> +        'is_filterable':fields.**boolean('Filterable?',
> help=MAGENTO_HELP),
> +        'is_comparable':fields.**boolean('Comparable?',
> help=MAGENTO_HELP),
> +        'is_searchable':fields.**boolean('Searchable ?',
> help=MAGENTO_HELP),
> +        'is_configurable':fields.**boolean('Configurable?',
> help=MAGENTO_HELP),
> +        'is_user_defined':fields.**boolean('User defined?',
> help=MAGENTO_HELP),
> +        'used_for_sort_by':fields.**boolean('Use for sort?',
> help=MAGENTO_HELP),
> +        'is_used_for_price_rules':**fields.boolean('Used for pricing
> rules?',
> +            help=MAGENTO_HELP),
> +        'is_used_for_promo_rules':**fields.boolean('Use for promo?',
> +            help=MAGENTO_HELP),
> +        'used_in_product_listing':**fields.boolean('In product listing?',
> +            help=MAGENTO_HELP),
>
> Theses are the lines I mentionned in my first email, and the MAGENTO_HELP
> ("Defined on Magento") help let my think that they are to configure on
> Magento. In the other hand, I just noticed that there are mappings for
> theses fields. So, finally, do we have to configure theses fields manually
> on Magento or not?
>
> If the whole configuration (except the group) of an attribute is exported
> to Magento but the group which remains to configure, it means that the
> point 2. is covered and that's fine for me.
>
> If it is only a matter of drag&dropping the attributes in their group, it
> is not much an issue for me (because this is done rapidly, unlike
> configuring all the fields above manually).
>
> But if some fields still need to be configured on Magento, that's an issue
> for me.
>
>
>
>> But on our side we have no choice the customer need to create the
>> attribut.option in OpenERP and also the attribut
>>
>> So I propose to extract the export of attribute in a separated module
>> that will be flag  as experimental, what do you think?
>>
> The export of the catalog without a synchro of the attributes in a way or
> another is not foreseeable, so we don't have much the choice here anyway.
>
>
>  And in this
>> module in a long term (and only if a customer ask for it) we may be able
>> to propose the export of group but this the restriction that every
>> backend will have exactly the same architecture (same group, same
>> position of attribute in group and also no posibility to manage the
>> position of the Magento system attribut).
>>
> Again, that's not about the group, but about all the configuration of an
> attribute.
>
>>
>> What do you think?
>>
>>
>>
>>
> Thanks for your work
>
>
> --
> 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/
>