magentoerpconnect-community team mailing list archive

[Douglas Morato <dfamorato@xxxxxxxxx>]

Hey Joel,

Thank you so much for your reply on the matter. You seem familiar with the "Partner Naming" workflow. Vianney told us that the base_partner_surname is deprecated . Can you confirm that statement is true and the module really contains deprecated functions or is just the matter of porting the module to v6.

I really agree with you on the on the matter that we can satisfy the magento-erpconnect module needs with creating 2 fields and still not breaking compatibility with the current ERP implementation.
 
I believe that is the cleanest implementation and I proposed them to be merged into the magento-erpconnect-v6 module. ( Personally, I think Openerp SA should 2 field name/sur_name change themselves because it is an informal standard on e-commerce solutions)



  
On Nov 4, 2010, at 2:35 AM, Joël Grand-Guillaume wrote:

> Dear all,
> 
> 
> The last suggestion done by Douglas Morato is exactly what is done into the base_partner_surname module ! It add 2 fields, and concatenate both in name with a function field.
> 
> I mean, adding a separator is not really a solution IMHO. We will be happy in the future I think to have 2 fields here ! It doesn't cost a lot, and as we say in french "Who can more, can less as well" ! It'll be easy with 2 field to deal with other situation (upgrade cause the customer wants to start using base_contacct, and so on...).
> 
> With only one field, we gonna have some "upgrade" difficulties. And also, all the reports will not be printed properly (or with a "/" !) unless you change them all to avoid that !
> 
> I think for those reason I vote for using base_partner_surname or adding this directly into the connector (may be better).
> 
> Regards,
> 
> Joël
> 
> 
> 
> 
> 
> Le 4 nov. 2010 à 03:07, Douglas Morato a écrit :
> 
>> On the practical side, I would like to recommend adding a new field for the last name. This would help a lot when integrating with other system, for example e-mail maketing.
>> 
>> It is so much more profession to refer to someone just by their last name on the header of an e-mail marketing.
>> 
>> Now, I don't really now how this is going to impact other modules or funcionatilies on the erp.
>> 
>> Maybe we need to create a First_Name and a Last_Name field and map these variables to magento and map the  concatenation of these 2 string into the partner name so it does not affect other modules.
>> 
>> 
>> 
>> On Nov 3, 2010, at 10:00 PM, Sharoon Thomas wrote:
>> 
>>> Hi All,
>>> 
>>> Can we not just add the new field for lastname in the res.partner.address
>>> 
>>> Its duplicating functionality of other module, but the other modules are a bloat for the purpose?
>>> 
>>> Thanks,
>>> 
>>> On Wed, Nov 3, 2010 at 9:54 PM, Jordi Esteve <jesteve@xxxxxxxxxxxxxxx> wrote:
>>> +1 for the solution 3/. It is not a clean solution but it is simple.
>>> 
>>> Jordi
>>> 
>>> En/na Vianney ha escrit:
>>>> 
>>>> Hello community, 
>>>> 
>>>> As we are improving the connector by allowing an update of the partners from OpenERP to Magento, we are facing a little issue, linked with a question asked by Guewen : 
>>>> https://answers.launchpad.net/magentoerpconnect/+question/132197
>>>> 
>>>> When importing the partners from Magento, it concatenates the Magento fields firstname and lastname to the OpenERP field name, so, when updating the data in Magento we lost information (the separation between the firstname and the lastname) 
>>>> 
>>>> We thought of three solutions and we would like your opinion on that : 
>>>> 1/ we can, as suggested by Guewen, use the base_partner_surname module (in extra modules) but it is deprecated and the strongly suggest to use the base_contact module (in addons) instead. 
>>>> 2/ we can so use this base_contact module but we think it is a very heavy module and maybe it is not such a good idea to use it for such a little benefit
>>>> 3/ we can simply change the mapping in the magentoerpconnect module to insert a separator between first and last names such as ' / ' so in OpenERP it will look like 'John / Doe' (note that it is the solution used now but the separator is simply ' ' and so it will not separate properly the first and last names when the first name is composed (Roberto Carlos for instance))
>>>> 
>>>> We think that the solution 3/ is better because it won't add complexity in the connector and we don't think it is problematic to introduce this '/' in the name field because it is easy to remove if needed (like in reports). 
>>>> 
>>>> So, what do you think? 
>>>> 
>>>> -- 
>>>> Vianney 
>>>> www.akretion.com.br 
>>>> <Mail Attachment.png>
>>>> 
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~magentoerpconnect-community
>>>> Post to     : magentoerpconnect-community@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~magentoerpconnect-community
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>   
>>> 
>>> 
>>> -- 
>>> Jordi Esteve
>>> Consultor Zikzakmedia SL
>>> jesteve@xxxxxxxxxxxxxxx
>>> Mòbil 679 170 693
>>> 
>>> Zikzakmedia SL
>>> Dr. Fleming, 28, baixos
>>> 08720 Vilafranca del Penedès
>>> Tel 93 890 2108
>>> 
>>> 
>>> 
>>> -- 
>>> Sharoon Thomas
>>> Business Analyst & Open Source ERP Consultant
>>> CEO @ http://openlabs.co.in
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~magentoerpconnect-community
>>> Post to     : magentoerpconnect-community@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~magentoerpconnect-community
>>> More help   : https://help.launchpad.net/ListHelp
>> 
> 
> -- 
> 
> Joël Grand-Guillaume 
> Division Manager
> Business Solutions
> 
> Camptocamp SA
> PSE A, CH-1015 Lausanne
> http://openerp.camptocamp.com/
> 
> Phone: +41 21 619 10 28
> Office: +41 21 619 10 10
> Fax: +41 21 619 10 00
> Email: joel.grandguillaume@xxxxxxxxxxxxxx
>

Attachment: smime.p7s
Description: S/MIME cryptographic signature