Tuesday, September 24, 2024
9 changes · saas-17.4
Resolved issues and error corrections
This fix prevents the Odoo inbox from crashing when certain notifications are created without a linked business record, such as moving an applicant to a new stage. Users can continue handling notifications in Odoo reliably, including rare messages that are not attached to a discussion thread.
Original PR description
To reproduce the error: - Set preference to Handle in Odoo - Move forward the applicant to the next stage - Inbox raise (Cannot read properties of undefined (reading 'message_needaction_counter_bus_id')) The error is due to the fact that the res_id is not set and so that the thread in the message is not correctly set. Also, guard message.thread in handling of mail.message/inbox because not all messages are linked to a thread and it makes sense functionally in rare case message is not linked to thread. https://github.com/odoo/enterprise/pull/70372 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users no longer lose an open dialog, such as a product search while creating a sales order, when they switch to another browser tab. This prevents unexpected interruptions and helps avoid losing context during data entry.
Original PR description
Problem: When a dialog is open on a form (e.g., searching for a product while creating a sale order), switching browser tabs causes the dialog to close unexpectedly. To fix this, we extend the solution from [this commit](https://github.com/odoo/odoo/commit/f59ed8d13e75868f58b33cd52ddd17590b690773) by preventing automatic saving if a dialog is currently open. Steps to reproduce: - Open any dialog on a form (e.g., search for a product while creating a sale order). - Switch to another browser tab. - The dialog closes. opw-4143092 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix restores expected keyboard behavior in Point of Sale number entry screens. Cashiers can again use Enter to confirm and Escape to cancel, preventing accidental character input and improving checkout flow reliability.
Original PR description
A change was made to simplify the number pad for point of sale, however, this change also removed the functionality of the enter and escape keys. This would cause the enter key to input a character instead of confirming. Adding the triggerAtEnter and triggerAtEscape config back to the number buffer allows this functionality to be restored. opw-4194518
Users can now open subcontracting details from receipts without encountering an error. This keeps the subcontracting workflow usable after recording received components and avoids disruption for purchasing and inventory teams.
Original PR description
Steps to reproduce the bug: - Create a storable product “P1” with the following BoM: - Type: subcontracting - subcontractor: Azure interior - Components: C1: - Route of C1: Resupply subcontractor on…
Steps to reproduce the bug:
- Create a storable product “P1” with the following BoM:
- Type: subcontracting
- subcontractor: Azure interior
- Components: C1:
- Route of C1: Resupply subcontractor on Order
- Create a purchase order:
- Vendor: Azure interior
- Product: 1 unit of P1
- Confirm the PO
- Go to the resupply of P1 and confirm it
- Go to the receipt and record the components
- Click on the subcontracting button
Problem:
An owl error is triggered:
```
Caused by: KeyNotFoundError: Cannot find key "subcontracting_portal_move_list_view" in the "views" registry
Error: Cannot find key "subcontracting_portal_move_list_view" in the "views" registry
```
The file is not included in the web_asset_backend bundle but only in the client bundle.
This bug was introduced after the following commit:
https://github.com/odoo/odoo/commit/f1749d3299957e2949e0b78653266a5397bb213c#diff-2395c9159b2ea0bf841d6f47ad8299bfa34fa516650acb55ae1392fa3aa32870L321-R328
Previously, if the key was not found when the backend was loaded, the default was used. However, now the key must be found in the registry, otherwise an error is thrown.
opw-4194661
opw-4184122
opw-4181126The point of sale tip popup now correctly reads amounts entered with local decimal separators, such as commas. This prevents tip amounts from being saved incorrectly for users working in languages or regions that do not use a dot as the decimal separator.
Original PR description
During [this refactoring] the custom `parseFloat` function import was removed from the payment screen. This custom function took into account the localized decimal separator to parse the entered number in the tip popup. By removing the import, the default JS `parseFloat` function was used, that only works with a `.` decimal separator. When you selected e.g. Spanish (Latin America) as a language that has `,` as a decimal separator, the payment screen would incorrectly parse the numeric string of the tip amount and cut off the part after the comma when saving it. This commit adds the correct `parseFloat` import again, so it works with localized separators. [this refactoring]: https://github.com/odoo/odoo/commit/2a5f1abf2e98ee09fa7a912b87d71879b5ff260b
The point of sale now prevents staff from selecting and selling product variants that have been archived. This helps avoid accidental sales of unavailable or discontinued items and keeps sales behavior aligned with product status.
Original PR description
Before this commit, users could inadvertently sell an archived product variant by selecting its attribute combination in the product configurator popup. opw-4171604 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Point of Sale orders now use the proper system-generated order reference instead of reusing the receipt number. This helps keep order tracking consistent across receipts, payments, and self-order flows.
Original PR description
Before this commit, the receipt number was incorrectly used as the order reference. This commit ensures that the order reference is correctly generated from the ir.sequence, aligning with the intended design. opw-4165620 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixed an issue that could incorrectly block connecting a bank journal to an online account when the journal had existing transactions but no currency set. If all existing transactions match the online account currency, the journal currency is now set automatically so the connection can proceed.
Original PR description
Commit https://github.com/odoo/enterprise/commit/a47e68a18fa478341efe21d82fa7f0e3e86e4c2c added an user error when trying to connect a bank journal with an online account that does not share the same currency, if there are already some moves created in that journal. The field currency_id being not required on the journal model, this error would also trigger when the currency_id was not set on the journal, but it contained only moves of the same currency as the account that we are trying to connect. An additional condition was added to the check, being that the journal has no currency set but the moves in that journal all use the same currency than the online account. If this is the case, the currency of the journal is set to the one from the online account. opw-[4177736](https://www.odoo.com/odoo/49/tasks/4177736) opw-[4148374](https://www.odoo.com/odoo/my-support-tasks/4148374)
This fixes an issue where moving a referral applicant to the next stage could break the Odoo inbox for users who handle notifications in Odoo. Notifications now stay linked correctly where possible, and rare messages without a related record are handled safely.
Original PR description
To reproduce the error: - Set preference to Handle in Odoo - Move forward the applicant to the next stage - Inbox raise (Cannot read properties of undefined (reading 'message_needaction_counter_bus_id')) The error is due to the fact that the res_id is not set and so that the thread in the message is not correctly set.