Monday, June 9, 2025
5 changes · saas-18.1
Miscellaneous changes
Description of the issue this PR addresses: - Trailing zeros in tab width styles cause test mismatches with browser-normalized values. Current behavior before PR: - Tests may use widths like "24.0px" which differ from browser output "24px". Desired behavior after PR is merged: - Tab widths use Number() conversion to match browser formatting and avoid test mismatches. task-4853029 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Por
Original PR description
Description of the issue this PR addresses: - Trailing zeros in tab width styles cause test mismatches with browser-normalized values. Current behavior before PR: - Tests may use widths like "24.0px" which differ from browser output "24px". Desired behavior after PR is merged: - Tab widths use Number() conversion to match browser formatting and avoid test mismatches. task-4853029 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#213313
If the `End Date` is already defined and the user removes that date in the form view of productivity losses, an error is generated. Steps to reproduce: --- - Install the `mrp` module - Manufacturing > Configuration > Work Centers > Open any of the Work Centers - In the form view of Work Center, click on the `Lost` stat button - Open a new Productivity Loss form, set a future date in `End Date`, click elsewhere, then clear the `End Date` Traceback: --- `TypeError: unsupported operand
Original PR description
If the `End Date` is already defined and the user removes that date in the form view of productivity losses, an error is generated. Steps to reproduce: --- - Install the `mrp` module - Manufacturing > Configuration > Work Centers > Open any of the Work Centers - In the form view of Work Center, click on the `Lost` stat button - Open a new Productivity Loss form, set a future date in `End Date`, click elsewhere, then clear the `End Date` Traceback: --- `TypeError: unsupported operand type(s) for -: 'bool' and 'datetime.timedelta'` If the end date is missing, we will return from the method sentry-6641245276 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#212204
*: sale_stock Issue: ====================== The forecast availability(icon) on the sales order incorrectly appears red even when enough stock is available for products in multi-step deliveries. Steps to Reproduce: ====================== 1. install sale_management & stock module. 2. Activate multi-step delivery in the warehouse. 3. Sell a product that has sufficient stock. 4. Ensure that enough quantities are reserved on the created picking. 5. Check the forecast availability(icon)
Original PR description
*: sale_stock Issue: ====================== The forecast availability(icon) on the sales order incorrectly appears red even when enough stock is available for products in multi-step deliveries. Steps…
*: sale_stock Issue: ====================== The forecast availability(icon) on the sales order incorrectly appears red even when enough stock is available for products in multi-step deliveries. Steps to Reproduce: ====================== 1. install sale_management & stock module. 2. Activate multi-step delivery in the warehouse. 3. Sell a product that has sufficient stock. 4. Ensure that enough quantities are reserved on the created picking. 5. Check the forecast availability(icon) on the sale order. Issue: ====================== The 'is_consuming' method is not considered for internal transfer moves during forecast availability computation. This leads to incorrectly flagging the forecast icon as red on the Sales Order, even when sufficient stock is available and reserved. With this commit: ====================== This fix ensures that the forecast icon correctly reflects stock availability by considering internal transfers in a multi-step delivery. the icon currently appears green on the Sales Order when there is enough stock to fulfill the demand. task - [4555666](https://www.odoo.com/odoo/project/966/tasks/4555666) Forward-Port-Of: odoo/odoo#199027
Steps: ----------- - Install the pos_l10n_se module. - Open a POS session with the Swedish Fiscal Data Module configured in the IoT Box settings. - Add a product to the order. Issue: ------------- - An error popup states: "Product has an invalid tax amount. Only 25%, 12%, 6% and 0% are allowed." even when the product is correctly configured with one of these tax rates. Cause: ---------- - The validation logic incorrectly applies conditions for displaying the error popup, mistakenly
Original PR description
Steps: ----------- - Install the pos_l10n_se module. - Open a POS session with the Swedish Fiscal Data Module configured in the IoT Box settings. - Add a product to the order. Issue: ------------- - An error popup states: "Product has an invalid tax amount. Only 25%, 12%, 6% and 0% are allowed." even when the product is correctly configured with one of these tax rates. Cause: ---------- - The validation logic incorrectly applies conditions for displaying the error popup, mistakenly rejecting valid tax rates when the PoS receipt label is set. FIX: ----------- - Updated the tax validation conditions to handle products correctly, allowing tax rates, and preventing false error messages. Extra Fix: ----------- - After resolving the above error, a new error popped up due to accessing `lst_price` from the product template. Resolved by updating `lst_price` to `list_price`. task-4687156 Forward-Port-Of: odoo/enterprise#83221
The aim of this commit is to provide a NIS code mapping for every country created by default in Odoo. Before this commit: If a 281.50 was created for someone in one of these countries, it would miss the `f2112_buitenlandspostnummer` field in the xml file resulting in the administration rejecting the file. After this commit: A pragmatic completion is made for those countries in `f2112_buitenlandspostnummer`. task: None Forward-Port-Of: odoo/enterprise#87081
Original PR description
The aim of this commit is to provide a NIS code mapping for every country created by default in Odoo. Before this commit: If a 281.50 was created for someone in one of these countries, it would miss the `f2112_buitenlandspostnummer` field in the xml file resulting in the administration rejecting the file. After this commit: A pragmatic completion is made for those countries in `f2112_buitenlandspostnummer`. task: None Forward-Port-Of: odoo/enterprise#87081