lp://staging/~jeffery9/ocb-addons/ocb-addons-fixups
- Get this branch:
- bzr branch lp://staging/~jeffery9/ocb-addons/ocb-addons-fixups
Branch merges
- Yannick Vaucher @ Camptocamp: Disapprove
- Stefan Rijnhart (Opener): Disapprove
- Pedro Manuel Baeza: Needs Information
-
Diff: 93 lines (+20/-5)6 files modifiedcrm/crm_lead.py (+5/-1)
crm/crm_phonecall_view.xml (+3/-3)
crm/wizard/crm_lead_to_opportunity.py (+3/-0)
crm/wizard/crm_lead_to_opportunity_view.xml (+1/-1)
crm/wizard/crm_partner_binding.py (+7/-0)
crm/wizard/crm_phonecall_to_phonecall_view.xml (+1/-0)
Related bugs
Related blueprints
Branch information
Recent revisions
- 9647. By jeffery chen fan
-
fix logical bugs in crm_lead2opport
unity_partner and _lead_create_ contact
that should not create dupcated partner - 9644. By Nicolas Vanhoren (OpenERP)
-
[FIX] problem with pads, the demo configuration doesn't work if the server is using https. I simply changed the url for the demo version.
- 9643. By Olivier Dony (Odoo)
-
[FIX] sale,sale_stock: sales analysis view using incorrect JOIN and group by clause
Similarly to the recent fixes in Purchase Analysis,
the Sales Analysis view must not group on the quantity
field. It is one of the columns that must be aggregated,
not used to fold PO lines into the same
result row.
The line count was also incorrect because of this, and
had to be corrected to actually count() the underlying
SO lines.In addition, the JOINs were done in the wrong order,
which could cause problems (e.g. if an empty SO ever
landed in the database, all the SO line columns
would be empty in the JOIN, and cause errors) - 9642. By Olivier Dony (Odoo)
-
[FIX] purchase: analysis view must not group by quantity, otherwise identical PO lines are counted only once
The product quantity is one of the columns that must be
aggregated, not used to fold PO lines into the same
result row.
This, combined with missing aggregation operators
was causing multiple identical PO lines from the
same PO to be merged together and only counted once
in some aggregations. - 9641. By Olivier Dony (Odoo)
-
[FIX] stock: no early currency rounding when computing average price
It is a common need to set a higher decimal precision
for `Product Price` (i.e. the product cost field) for
high volume / low value items. This may typically
require up to 4-6 decimals for e.g. EUR/USD-based
companies where the currency has 2 decimals.
In that case the product cost should be stored with
full precision without applying the currency rounding.
The appropriate currency rounding will be applied
anyway as soon as a transaction actually uses that
product cost (typically in a SO/PO) - 9640. By Holger Brunn (Therp)
-
[FIX] resolve conflict between
http://bazaar. launchpad. net/~ocb/ ocb-addons/ 7.0/revision/ 9584
and
http://bazaar. launchpad. net/~openerp/ openobject- addons/ 7.0/revision/ 9564 - 9639. By Olivier Dony (Odoo)
-
[FIX] stock: `product cost` field in partial picking wizard must respect decimal precision
Without the right precision the default rounding is
applied and causes a possible loss of precision when
the `Product Price` precision is increased.
This can in turn lead to incorrect average price
computations.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp://staging/ocb-addons