summaryrefslogtreecommitdiff
path: root/addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js
diff options
context:
space:
mode:
authorNicolas Martinelli <nim@odoo.com>2016-10-26 10:46:00 +0200
committerNicolas Martinelli <nim@odoo.com>2016-10-26 10:57:16 +0200
commite99e0d6922742500ecb222b7667a85fe9220863f (patch)
tree8f99d3f9f3095aca1d5014517cf283f6cddf4f63 /addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js
parent19cca50e7c8d7e6b86f3851398725ce64694b063 (diff)
[FIX] point_of_sale: journal of closing entries
- Invoice a POS order => the invoice number is for example 0001 - Close the POS session - Invoice another POS order => the invoice number is 0003 This is because the journal used for the POS closing entries is the same than the journal used for the customer invoices. Therefore, the closing entry consumes a sequence number of the invoices. This affects POS orders, but potentially SO as well if they use the same journal. This is fixed in v10 from commit b5b0d36b31. In v9, we use a workaround by looking first if a `ir.config_parameter` named `pos.closing.journal_id` exists. We use this journal for the session closing. opw-691771
Diffstat (limited to 'addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js')
0 files changed, 0 insertions, 0 deletions