c2c-oerpscenario team mailing list archive
-
c2c-oerpscenario team
-
Mailing list archive
-
Message #01478
[Bug 667735] Re: OpenERP fixed stock_move.date_planned typo on OpenERP v6, we are impacted.
Update file sale.py line 181 from :
recent_move_ids = self.pool.get('stock.move').search(cr, uid,
[('date_planned', '>', shop.last_inventory_export_date), ('product_id',
'in', product_ids), ('state', '!=', 'draft'), ('state', '!=',
'cancel')])
to
recent_move_ids = self.pool.get('stock.move').search(cr, uid,
[('date_expected', '>', shop.last_inventory_export_date), ('product_id',
'in', product_ids), ('state', '!=', 'draft'), ('state', '!=',
'cancel')])
All done :)
--
OpenERP fixed stock_move.date_planned typo on OpenERP v6, we are impacted.
https://bugs.launchpad.net/bugs/667735
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: New
Bug description:
Hello,
Looks like OpenERP SA finally took care of that renaming the stock_move.date_planned field into stock_move.date_expected on OpenERP v6.
the magentoerpconnect module should follow that change on the v6 serie. A trivial sed script will do it.
We should ensure that date_expected is what stands for date_planned though.
References