Skip to content
Snippets Groups Projects
  1. Nov 28, 2014
  2. Nov 07, 2014
  3. Nov 05, 2014
  4. Nov 03, 2014
  5. Oct 24, 2014
    • Martin Trigaux's avatar
      [FIX] product: pricelist, uom and price_surcharge · 79ebe106
      Martin Trigaux authored
      The price_surcharge attribute must be computed based on the reference unit of measure (divided by the factor).
      This is to make sure than 12 units and 1 dozen have the same price after pricelist computation (opw 599727).
      
      Added test checking the correctness of pricelist computation based on unit of measures.
      79ebe106
  6. Oct 15, 2014
  7. Sep 09, 2014
  8. Jul 06, 2014
    • Raphael Collet's avatar
      [MERGE] new v8 api by rco · cbe2dbb6
      Raphael Collet authored
      A squashed merge is required as the conversion of the apiculture branch from
      bzr to git was not correctly done. The git history contains irrelevant blobs
      and commits. This branch brings a lot of changes and fixes, too many to list
      exhaustively.
      
      - New orm api, objects are now used instead of ids
      - Environements to encapsulates cr uid context while maintaining backward compatibility
      - Field compute attribute is a new object oriented way to define function fields
      - Shared browse record cache
      - New onchange protocol
      - Optional copy flag on fields
      - Documentation update
      - Dead code cleanup
      - Lots of fixes
      cbe2dbb6
  9. Jul 02, 2014
  10. Jun 25, 2014
  11. May 27, 2014
  12. Mar 17, 2014
  13. Mar 06, 2014
  14. Mar 05, 2014
  15. Feb 12, 2014
  16. Feb 11, 2014
    • Martin Trigaux's avatar
      [FIX] pricelist: correctly take into account uom when computing pricelists... · ebdb2306
      Martin Trigaux authored
      [FIX] pricelist: correctly take into account uom when computing pricelists based on supplier price on product form (opw 595881)
      
      The previous behaviour used the uom of product while it could be a different one selected (by default the purchase unit of measure for purchase orders).
      This was an issue especially when having different uom with supplier info lines setting degressive prices. The price should be computed based on selected uom and not the product uom.
      
      bzr revid: mat@openerp.com-20140211145703-9uut4hw9aqh7326o
      ebdb2306
  17. Dec 09, 2013
  18. Dec 06, 2013
  19. Sep 06, 2013
    • Olivier Dony's avatar
      [FIX] product: support string values for context `pricelist` key when computing prices · 6de00513
      Olivier Dony authored
            
            As of v7 search views will replace the value of any `self`
            literal in a @context attribute by the name of the
            record, whereas it used to be its ID.
            This means that the `Pricelist` filter used to display
            the product list with a specific pricelist would not
            work anymore.
            
            The fix requires a rather hackish name_search()
            override for product.pricelist because the display
            name of pricelists includes their currency, while
            that could be a valid name for a pricelist too.
            
            To avoid side-effects the name_search() override
            only picks up the special case used by the
            product.product._product_price() method when it
            tries to apply the context pricelist, that is
            with operator explicitly set to `=` and no extra
            domain `args`.
      
      lp bug: https://launchpad.net/bugs/1178835 fixed
      
      bzr revid: odo@openerp.com-20130906155047-7dmozy2jpe1ca1p2
      6de00513
  20. Jul 12, 2013
  21. May 29, 2013
  22. May 17, 2013
  23. Apr 15, 2013
  24. Mar 21, 2013
  25. Mar 15, 2013
  26. Dec 14, 2012
  27. Dec 06, 2012
  28. Oct 23, 2012
  29. Oct 09, 2012
  30. Sep 25, 2012
  31. Sep 24, 2012
Loading