Thursday, September 5, 2024
10 changes · 17.0
Enhancements to existing features
The Point of Sale IoT Box image now includes an additional authentication library needed for newer image builds. Developers also get a shortcut to reset IoT Boxes on development branches, making testing and maintenance easier without changing everyday user workflows.
Original PR description
We add pyotp python lib to have it in the IoT Box image v24.08. We also add an alias to reset the IoT Box on a dev branch.
Resolved issues and error corrections
Fixes a display issue in Point of Sale where receipt previews on the Odoo mobile app could show mismatched background colors. Receipts now use a transparent background so the text area and overall receipt background appear consistent, improving the print preview experience for cashiers.
Original PR description
When trying to print the receipt on the Odoo app on a mobile device, the background color of the receipt would be different than the background color of the text Steps to reproduce: ------------------- * Open PoS on the Odoo app * Print receipt > Observation: On the preview the receipt looks like this  Why the fix: ------------ By making the background color transparent we ensure that it will always be the same for the text and the general background color opw-4094591 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
- Before this commit The ir.asset target field is only displayed when the directive is 'replace', but this field is required for 'after' and 'before' directives too. - After this commit The form view is adapted to fix this issue. Forward-Port-Of: odoo/odoo#178765
Original PR description
- Before this commit The ir.asset target field is only displayed when the directive is 'replace', but this field is required for 'after' and 'before' directives too. - After this commit The form view is adapted to fix this issue. Forward-Port-Of: odoo/odoo#178765
Users can now assign a responsible person to a picking batch directly from the kanban view without hitting an error. This prevents a small workflow interruption in warehouse batch management and keeps the assignment process consistent across views.
Original PR description
This commit fixes the error that was triggered when trying to assign a responsible user for a picking batch from the kanban view of batches. The error was thrown because the `user_id` field depends on `company_id` field in its domain, which was not existent in the kanban view. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
French localized invoices now format customer address details correctly when the customer has a parent company. This prevents printed invoices from showing jumbled text in a single column, improving document readability for affected French accounting users.
Original PR description
Steps to reproduce: - Download french accounting localization module - Switch company to 'FR Company' - Accounting > Customers > Invoice > New - Pick a customer with a parent company - Confirm > Gear > Print > Invoice Results in a formatting error that prints jumbled text in one column. This happens because of a conditional field that did not receive the update last time in 9674b4eeb26bfb7dd09d48b81bb8c27601e6990a. opw-3865644 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Enable global rounding Have a company currency with 0 decimal precision digits Have a foreign currency with 2 decimal precision digits Create a Pricelist for the foreign currency Create a Sale Order Set the foreign currency pricelist Add an order line with price 15.31 and 19% tax (not included) Issue: system will compute a price tax of 3.00, price total of the line will be 18.31 Order total is correct (18.22) This occurs because, when `_compute_taxes` aggregates results https://gi
Original PR description
Enable global rounding Have a company currency with 0 decimal precision digits Have a foreign currency with 2 decimal precision digits Create a Pricelist for the foreign currency Create a Sale Order…
Enable global rounding Have a company currency with 0 decimal precision digits Have a foreign currency with 2 decimal precision digits Create a Pricelist for the foreign currency Create a Sale Order Set the foreign currency pricelist Add an order line with price 15.31 and 19% tax (not included) Issue: system will compute a price tax of 3.00, price total of the line will be 18.31 Order total is correct (18.22) This occurs because, when `_compute_taxes` aggregates results https://github.com/odoo/odoo/blob/0e1e7bf9c96b8fe4a06dfe3f858a837a8fdf386d/addons/account/models/account_tax.py#L1159-L1162 it will consider a tax amount that, in global rounding, is rounded according to company currency, that does not have the same precision settings https://github.com/odoo/odoo/blob/0e1e7bf9c96b8fe4a06dfe3f858a837a8fdf386d/addons/account/models/account_tax.py#L1011-L1014 A solution is to directly call `_compute_taxes_for_single_line` is order to get the raw results for the single line opw-4050736 Forward-Port-Of: odoo/odoo#176187
model.default_get should use a list of field names as input but not a field name Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#179092
Original PR description
model.default_get should use a list of field names as input but not a field name Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#179092
Account moves are created for the whole session and are not specific to a pos order. So we shouldn't map the accounts used. This reverts commit 595561fd9b48b5a71bf709b018d25006deb9f12c. opw-4086609 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#179084
Original PR description
Account moves are created for the whole session and are not specific to a pos order. So we shouldn't map the accounts used. This reverts commit 595561fd9b48b5a71bf709b018d25006deb9f12c. opw-4086609 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#179084
The base two variants of the generic_tax_report : (generic_tax_report_tax_account, generic_tax_report_account_tax) had the availability_condition set to country with no country_id. The expected result was to have the availability_condition set to always as no country_id is set. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#178950
Original PR description
The base two variants of the generic_tax_report : (generic_tax_report_tax_account, generic_tax_report_account_tax) had the availability_condition set to country with no country_id. The expected result was to have the availability_condition set to always as no country_id is set. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#178950
This Fix addresses an issue where a traceback error occurs if the invoice date is not set when creating a landed cost. To reproduce the issue: 1. Create a service product and set it as a landed cost product. 2. Create and validate a customer invoice for this product. 3. Reset the invoice to draft status. 4. Clear the date on the invoice. 5. Click on the "Create Landed Cost" button. Error: A traceback occurs due to a failed assertion statement: "convert amount from unknown date". Th
Original PR description
This Fix addresses an issue where a traceback error occurs if the invoice date is not set when creating a landed cost. To reproduce the issue: 1. Create a service product and set it as a landed cost product. 2. Create and validate a customer invoice for this product. 3. Reset the invoice to draft status. 4. Clear the date on the invoice. 5. Click on the "Create Landed Cost" button. Error: A traceback occurs due to a failed assertion statement: "convert amount from unknown date". This fix ensures that the date is always populated when creating a new landed cost record. If the invoice date is not set, the current date will be used. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#175788