If sequence is not defined on default,may cause problems of sorting!
Bug #586300 reported by
os33
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Odoo Addons (MOVED TO GITHUB) |
Fix Released
|
Low
|
Unassigned | ||
| Odoo Web Client |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Hello,
I installed the service profile + account_
When I create an invoice with the 'Invoice on analytic entries' wizard all the sequence of the lines are 0 : OK
On the invoice, if I add new lines with an higher sequence the first lines (with sequence=0) stay at the end (even when saved) so it's very difficult to have a "preview" of the invoice with sub total etc
NB: The web client orders correctly the added lines except if some lines are still present (with sequence=0) but by saving the invoice all the lines are in the right order.
Thanks
Related branches
Revision history for this message
| os33 (olivier-sommier) wrote | #1 |
Revision history for this message
| os33 (olivier-sommier) wrote | #2 |
| Changed in openobject-client: | |
| status: | New → Confirmed |
| Changed in openobject-client-web: | |
| status: | New → Confirmed |
| Changed in openobject-client: | |
| importance: | Undecided → Medium |
| summary: |
- Lines in Invoices :Wrong order + Sequence Problem : If O2M contains a line with seq=0, new lines won't + compete with that line in Sorting! |
Revision history for this message
| Jay Vora (Serpent Consulting Services) (jayvora) wrote | #3 |
| summary: |
- Sequence Problem : If O2M contains a line with seq=0, new lines won't - compete with that line in Sorting! + If sequence is not defined on default,may cause problems of sorting! |
| Changed in openobject-client-web: | |
| milestone: | none → 5.0.11 |
| status: | Confirmed → Invalid |
| affects: | openobject-client → openobject-addons |
| Changed in openobject-addons: | |
| importance: | Medium → Low |
| milestone: | none → 5.0.11 |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
The bug occurs in web client too