Daily updates from Odoo
Monday, September 23, 2024
3 changes · master
Resolved issues and error corrections
Fixes an issue where quotation calculators could fail or load the wrong sales order lines when synced fields targeted positions above the first line. Saving from the spreadsheet is now more reliable and avoids unnecessary reloading when all line positions are already available.
Fixed an issue in the Barcode app where scanning a non-GS1 product barcode together with multiple serial numbers could cause an error when GS1 nomenclature was enabled. This helps warehouse users continue receipt operations smoothly and prevents stuck scan counts on screen after failed parsing.
Original PR description
How to reproduce ================ - Create a product tracked by SN and set a barcode (ex.: productserial1) - Select the Default GS1 Nomenclature in the Inventory Settings - Open the Barcode App > Operations > Receipts > New - Scan a barcode containing the created product's barcode and multiple serial numbers (eg.: 'productserial1,sn1,sn2,sn3,sn4') --> Traceback. Cause of the issue ================== There is two issues: 1. The parser throws an error if it tries to parse a barcode with the GS1 nomenclature and fails and this error wasn't handle bv the BarcodeObject when it parses its barcode. 2. If the BarcodeObject wasn't parsed and has no missing record, it wasn't processed and the barcode's count stay on the screen.
Resource-based appointments booked online now show correctly in the Gantt planning view. This prevents missed bookings in operational schedules by removing an inappropriate privacy check for events that are tied to resources rather than individual users.
Original PR description
Purpose ======= Fix the resource events which weren't displayed in the gantt view when booked from the front-end. Specification ============= When an appointment based on resources is booked from the front-end, the event "user_id" field is set to be OdooBot. This is an issue as the read_group domain for the calendar.event model checks the user_id 'res_users_settings_id' field for privacy purpose but OdooBot doesn't have any users settings. => The read_group domain is always evaluated to False. No resource based events booked from the front-end are displayed on the gantt view. Fixing that by updating the privacy domain to be sure every events related to a resource can now be visible and accessible on the gantt view. The privacy field of an event is mainly related to the user settings but resource events aren't typically linked to any user meaning their visibility shouldn't depend on the privacy. Task-4191434