Monday, May 26, 2025
6 changes
1 change
Resolved issues and error corrections
ESG Initiative pages now keep the correct web address instead of showing a generic tasks link. This prevents crashes when users copy the link to another browser or enter and leave Studio, making the ESG workflow more reliable.
Original PR description
Have esg_project installed Got to ESG => Act => Initiatives Check the url Before this commit, the url was /odoo/tasks. This posed a number of issues: - Copying this URL in another browser crashed because the context of this action was lost - Entering then leaving studio crashed too, for the same reason. After this commit, the path of the action is correct and reloading it in another browser works correctly. runbot-error-198568
5 changes
Resolved issues and error corrections
This fix automatically matches Point of Sale customer account charges with their related settlements. It prevents settled POS amounts from incorrectly appearing as available credit for other invoices, reducing customer billing confusion.
Original PR description
### Problem When paying a PoS order using customer account, an account move line debiting Account Receivable will be created. Settling this amount inside the PoS (by depositing money) will create…
### Problem
When paying a PoS order using customer account, an account move line debiting Account Receivable will be created. Settling this amount inside the PoS (by depositing money) will create another account move line crediting Account Receivable (represents the payment). The second move line is considered, by Odoo, as an outstanding amount, and this amount can be used to pay another invoice (sale order invoice). The moves affecting Account Receivable are still correct. However, unreconciling the two lines created from PoS will cause a confusion for clients who may use this amount to pay other invoices.
This PR covers versions 18 & 18.1, as reconciliation logic differs in later versions.
### How to reproduce
* Open a PoS session.
* Create an order and pay using customer account.
* Settle this customer's account (inside PoS).
* Create a Sale Order and invoice it (or just an invoice).
* The amount settled can be used as outstanding amount and can be used to pay the created invoice.
enterprise PR: https://github.com/odoo/enterprise/pull/86174
18.2 PR: https://github.com/odoo/odoo/pull/210619
opw-4794793This update refreshes Odoo's spreadsheet component with several fixes that make spreadsheet reports and calculations more reliable. It improves monthly pivot sorting, localized text, chart stability, scrolling behavior, autocomplete suggestions, and Excel export compatibility.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/838c4f799 [REL] 18.0.30 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0)…
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/838c4f799 [REL] 18.0.30 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0) https://github.com/odoo/o-spreadsheet/commit/9600da59c [FIX] pivot: `month` granularity sorting [Task: 4781810](https://www.odoo.com/odoo/2328/tasks/4781810) https://github.com/odoo/o-spreadsheet/commit/75db485fa [FIX] ComposerStore: placeholder should be localized [Task: 4817738](https://www.odoo.com/odoo/2328/tasks/4817738) https://github.com/odoo/o-spreadsheet/commit/e5ac913c2 [FIX] Spreadsheet: reset scroll inertia after some time [Task: 4813296](https://www.odoo.com/odoo/2328/tasks/4813296) https://github.com/odoo/o-spreadsheet/commit/3b725faa8 [FIX] auto_complete: showing all proposal on single match [Task: 4735015](https://www.odoo.com/odoo/2328/tasks/4735015) https://github.com/odoo/o-spreadsheet/commit/1540b923d [IMP] xlsx: prevent exporting the SPLIT function [Task: 4766568](https://www.odoo.com/odoo/2328/tasks/4766568) https://github.com/odoo/o-spreadsheet/commit/c70f57360 [IMP] xlsx: prevent exporting FILTER function [Task: 4766579](https://www.odoo.com/odoo/2328/tasks/4766579) https://github.com/odoo/o-spreadsheet/commit/aebb77cc2 [FIX] chart: charts changing size on update [Task: 4794364](https://www.odoo.com/odoo/2328/tasks/4794364) https://github.com/odoo/o-spreadsheet/commit/6f0b45310 [FIX] module logical: keep functional behavior on empty ref [Task: 4775222](https://www.odoo.com/odoo/2328/tasks/4775222) https://github.com/odoo/o-spreadsheet/commit/f06d512ba [FIX] module logical: vectorize only if valid expression [Task: 4775222](https://www.odoo.com/odoo/2328/tasks/4775222) Co-authored-by: Anthony Hendrickx (anhe) <anhe@odoo.com> Co-authored-by: Alexis Lacroix (laa) <laa@odoo.com> Co-authored-by: Lucas Lefèvre (lul) <lul@odoo.com> Co-authored-by: Dhrutik Patel (dhrp) <dhrp@odoo.com> Co-authored-by: Adrien Minne (adrm) <adrm@odoo.com> Co-authored-by: Mehdi Rachico (mera) <mera@odoo.com> Co-authored-by: Florian Damhaut (flda) <flda@odoo.com> Co-authored-by: Rémi Rahir (rar) <rar@odoo.com> Co-authored-by: Pierre Rousseau (pro) <pro@odoo.com> Co-authored-by: Vincent Schippefilt (vsc) <vsc@odoo.com>
This fix prevents an error when a Point of Sale session is opened on multiple devices and then removed from one of them. Staff using another device will no longer hit a confusing missing-session error during opening control, improving reliability at store opening.
Original PR description
Before this commit, if a POS session was open on two devices and the session was removed from one device, attempting to proceed with the opening control on the other device would result in a missing error. Steps to reproduce: 1. Open a POS session on device 1 and 2 (both at the opening control) 2. On device 1, remove the session by clicking on backend 3. On device 2, attempt to set the opening control After this commit, the system properly handles the case where the session has been removed, preventing the missing error and improving user experience. opw-4775255 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Replenishment no longer unnecessarily deletes and recreates orderpoints that users have manually adjusted. This helps keep configured minimum and maximum quantities intact while reducing wasted system work when reopening replenishment.
Original PR description
**Current behavior:** Everytime the Replenishment action is called we delete and recreate lots of (default) orderpoints. Sometimes it's annoying because manual values may have been set on them and in…
**Current behavior:**
Everytime the Replenishment action is called we delete and
recreate lots of (default) orderpoints. Sometimes it's annoying
because manual values may have been set on them and in general
it is wasteful.
**Expected behavior:**
Don't delete an orderpoint if either it's product min/max qty
fields have non-default values, don't delete/create orderpoints
if not necessary.
**Steps to reproduce:**
1. Create a delivery for (storable) product
2. Open replenishment -> edit auto-gen orderpoint to have 5
min/max qty
3. Go to dashboard, re-open replenishment -> the edited record
was deleted and there is a new one with the default `0`
min/max qty
**Cause of the issue:**
`_search_qty_to_order` does not really respect a domain leaf
like:
`('qty_to_order', '<=', 0)`
because currently it satisfied by `qty_to_order_manual==0`,
irrespective of `qty_to_order_computed`.
**Fix:**
Make `_search_qty_to_order` stricter by taking the intersection
of searching `qty_to_order_manual` and `qty_to_order_computed`
instead of the union.
opw-4547116Settling a customer's due balance in Point of Sale now automatically matches the related accounting entries. This prevents the same settled amount from appearing as available credit for other invoices, reducing confusion and keeping customer receivables accurate.
Original PR description
- This commit ensures that when settling due amounts in the Point of Sale (POS), the account move lines (aml) are automatically reconciled. This is particularly important for customer accounts, where…
- This commit ensures that when settling due amounts in the Point of Sale (POS), the account move lines (aml) are automatically reconciled. This is particularly important for customer accounts, where due amounts need to be accurately reflected in the financial records.
- This commit also adds a test to ensure that account move lines (aml) are properly reconciled when settling due amounts in the POS.
### Problem
When paying a PoS order using customer account, an account move line debiting Account Receivable will be created. Settling this amount inside the PoS (by depositing money) will create another account move line crediting Account Receivable (represents the payment). The second move line is considered, by Odoo, as an outstanding amount, and this amount can be used to pay another invoice (sale order invoice). The moves affecting Account Receivable are still correct. However, unreconciling the two lines created from PoS will cause a confusion for clients who may use this amount to pay other invoices.
### How to reproduce
* Open a PoS session.
* Create an order and pay using customer account.
* Settle this customer's account (inside PoS).
* Create a Sale Order and invoice it (or just an invoice).
* The amount settled can be used as outstanding amount and can be used to pay the created invoice.
Community PR: https://github.com/odoo/odoo/pull/211166
opw-4794793
Co-authored-by: Majed Alhanash (malh) <malh@odoo.com>