Merge lp:~openerp-dev/openobject-addons/trunk-bug-724131-rpa into lp:openobject-addons
Proposed by
Rucha (Open ERP)
Status: | Merged |
---|---|
Merged at revision: | 5691 |
Proposed branch: | lp:~openerp-dev/openobject-addons/trunk-bug-724131-rpa |
Merge into: | lp:openobject-addons |
Diff against target: |
192 lines (+81/-57) 3 files modified
account_anglo_saxon/purchase.py (+3/-3) purchase/purchase.py (+75/-51) purchase_analytic_plans/purchase_analytic_plans.py (+3/-3) |
To merge this branch: | bzr merge lp:~openerp-dev/openobject-addons/trunk-bug-724131-rpa |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Rucha (Open ERP) | Pending | ||
qdp (OpenERP) | Pending | ||
Review via email: mp+82254@code.launchpad.net |
This proposal supersedes a proposal from 2011-11-14.
Description of the change
lp:724131: Fixed missing relation between PO line and Invoice line when purchase order invoice control is Based on generated invoice,
To post a comment you must log in.
Hello Rucha,
just few comments: invoice_ line_data( ), in order to increase the inheritability and flexibility of our code
1) can you make a new function to retrieve the dict to use to create the invoice line, _prepare_
2) really strange: i didn't know that the field invoice_id on account. invoice. line wasn't mandatory! anyway, for performance reasons it would be better to create the invoice with no lines, then to create the lines with the invoice_id set.
3) i don't like this syntax. Is there a reason to do it? a good one? if no, i propose that you let it like that to keep the code as much consistent as possible. {'invoice_ ids': [(4, inv_id)]})
75 - self.write(cr, uid, [o.id], {'invoice_ids': [(4, inv_id)]})
78 + o.write(
4) we need more comments, more docstrings in the new functions
5) some context may be added in function calls, from here to there, in the lines you already changed
Thanks