c2c-oerpscenario team mailing list archive

[Quentin THEURET <quentin@xxxxxxxxxxx>]

** Patch added: "invoice_internal_number.patch"
   https://bugs.launchpad.net/bugs/677398/+attachment/1738081/+files/invoice_internal_number.patch

** Description changed:

  On the invoice views, the shown number is not the invoice number : it's
  the number of the related move.
  
  To fix that, you must replace all occurencies of the 'number' field of
  an invoice by the 'internal_number' on all views of invoices.
  
- 
- The second bug is the computation of this internal number. It exists a sequence to create this internal number, but it's not use by the system now.
+ The second bug is the computation of this internal number. It exists a
+ sequence to create this internal number, but it's not use by the system
+ now.
  
  I attach a patch to correct these two problems but i think that the
- field 'number' is used at the place of the field 'internal_number' which
- is more comprehensive for people.
+ field 'number' is used instead of the field 'internal_number' which is
+ more comprehensive for people.

-- 
[6.0 trunk] Invoice number not correct
https://bugs.launchpad.net/bugs/677398
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Addons Modules: New

Bug description:
On the invoice views, the shown number is not the invoice number : it's the number of the related move.

To fix that, you must replace all occurencies of the 'number' field of an invoice by the 'internal_number' on all views of invoices.

The second bug is the computation of this internal number. It exists a sequence to create this internal number, but it's not use by the system now.

I attach a patch to correct these two problems but i think that the field 'number' is used instead of the field 'internal_number' which is more comprehensive for people.