c2c-oerpscenario team mailing list archive
-
c2c-oerpscenario team
-
Mailing list archive
-
Message #03503
[Bug 670856] Re: Delivery carrier mapping correction
"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."
I agree with you, it would work, I said it isn't a problem for me.
But I raise the fact that we have to store the shipping method in a different field than the carrier code. It could be stored in the name as you propose, thereby we still have to modify the shipping_method mapping like that :
if ifield:
carrier_ids = self.pool.get('delivery.carrier').search(cr, uid, [('name', '=', ifield)])
if carrier_ids:
result=[('carrier_id', carrier_ids[0])]
else:
result=[]
Thanks,
Guewen
--
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
References