c2c-oerpscenario team mailing list archive

["Vianney - www.akretion.com.br" <670856@xxxxxxxxxxxxxxxxxx>]

Well we thought about it and here what we came with :

First we thought we could indeed map only the carrier and keep the
shipping method in a filed in the sale order. But the problem here is
that it doesn't help a lot because you want to have this information in
the picking as well. So how to pass the information? We can create a new
object and pass it on but it will be a bit heavy...

So we think we will stick with this solution, but I don't understand
your point, why wouldn't it work, if you have n carriers (real carriers)
and for each m shipping methods, you "just" have to register in OpenERP
m x n carriers whose names are carrierid_shippingmethod. This way you
store the shipping method and the carrier under the carrier_id. Sure
this is not optimal but this will work and the other solution is far
heavier to implement.

Let me know if I missed something!

Thank you

-- 
Delivery carrier mapping correction
https://bugs.launchpad.net/bugs/670856
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in Magento Open ERP Connector: Confirmed

Bug description:
Hello,

I just tested the delivery carrier mapping from Magento to OpenERP with the revision http://bazaar.launchpad.net/~openlabs-akretion-consortium/magentoerpconnect/magentoerpconnect/revision/346

The condition to map the carrier is inverted, it will never be updated in OpenERP ;-)

Here is a patch with the correction.

Thanks
Guewen