Skip to content
Snippets Groups Projects
  1. Nov 08, 2017
  2. Nov 06, 2017
    • Christophe Simonis's avatar
      928a284b
    • Nicolas Martinelli's avatar
      [FIX] sale_expense: fields consistency · 08ab28a6
      Nicolas Martinelli authored
      Use case to reproduce:
      - Set a product to be expensed
      - Set the expense_policy to something else than no
      - Do a delivery order with a picking
      - Validate the picking
      -> Delivered quantity to 0 and impossible to create an invoice
      if the invoice_policy is delivered_quantity
      
      It happens due to this commit 48ea59d4
      What does it do:
      - The move could be generated by an expense.
      - If the move has 'no' as expense policy thus we won't add it in the invoice
      Problem we can't guess if the move come from an expense or not (limitation).
      
      This commit add an onchange on can_be_expense is order to set the expense
      policy back to 'no' when the user uncheck it.
      
      Courtesy of amoyaux
      
      opw-777139
      08ab28a6
    • Christophe Simonis's avatar
      88c641e6
  3. Nov 05, 2017
  4. Nov 03, 2017
  5. Nov 02, 2017
  6. Oct 31, 2017
  7. Oct 30, 2017
  8. Oct 29, 2017
  9. Oct 27, 2017
Loading