Tuesday, October 22, 2024
17 changes · 17.0
Enhancements to existing features
This update adds a small extension point that helps Odoo handle foreign VAT information more reliably when fiscal position logic is customized. It mainly supports a related Enterprise fix and improves maintainability without changing day-to-day user workflows.
Original PR description
This hook is used for fix in the corresponding enterprise commit. We do it this way instead of defining everything in enterprise for clarity and robustness.
The point-of-sale customer display no longer shows an unwanted white background in table sections. This keeps the IoT display visually consistent and easier to read for users.
Original PR description
Bootstrap adds an ugly white background to `table` tags when we add the `table` class. We now force it to be transparent.
Resolved issues and error corrections
The withholding wizard now prevents users from manually changing the calculated TDS amount. This helps keep TDS values consistent with the base amount and selected tax, reducing the risk of accidental reporting or accounting errors.
Original PR description
Before this commit: The TDS amount in the wizard was editable, so users were able to change it manually. After this commit: The TDS amount in the wizard is now read-only and can’t be changed, since it’s calculated based on the base amount and TDS tax.
Miscellaneous changes
Fixes a rounding issue where the cost of kit components is rounded too early in the stock valuation process, leading to discrepancies in the final stock valuation layer values. The kit's total cost was being calculated with an early rounding step, which caused a small mismatch between the expected and actual values. This fix ensures that the correct unit cost is used in the stock valuation layer without affecting the product's standard price. Example: 1.) Create Product A: Storable Product
Original PR description
Fixes a rounding issue where the cost of kit components is rounded too early in the stock valuation process, leading to discrepancies in the final stock valuation layer values. The kit's total cost…
Fixes a rounding issue where the cost of kit components is rounded too early in the stock valuation process, leading to discrepancies in the final stock valuation layer values. The kit's total cost was being calculated with an early rounding step, which caused a small mismatch between the expected and actual values. This fix ensures that the correct unit cost is used in the stock valuation layer without affecting the product's standard price. Example: 1.) Create Product A: Storable Product Type Route = Manufacturing Category = AVCO or FIFO 2.) Create Product B: Storable Product Type Routes = Buy Category = AVCO or FIFO 3.) Make a BOM Product A Quantity = 1 Kit Components: 12 units of Product B 4.) Create a Purchase Order: Buy 1 unit of Product A at $100 5.) Confirm PO -> this will generate a receipt 6.) Validate receipt 7.) Note the valuation is 12 units @ a value of 99.96 where it should be 100 Current behavior before PR: svl.value = 99.96 Desired behavior after PR is merged: svl.value = 100 opw-4208554 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#183267
The inventory workflow now blocks users from entering expiration dates for products that are not tracked. This prevents misleading product records and keeps expiry information limited to items where tracking is enabled.
Original PR description
**Steps to reproduce the bug:** - Enable the "Expiration Date" feature in inventory settings. - Create a non-tracked product "P1". - Create a receipt with one unit of P1. - Mark it as "To Do". - Go to the detailed operation. **Problem:** You are able to set an expiration date even though the product is not tracked. opw-4256125
A typo in a Point of Sale error message was fixed by adding a missing space. This makes the message clearer for users and improves the overall polish of the interface.
Original PR description
An error message was missing a space in between "a" and "hamburger" in "ahamburger". This commit fixes this typo. Task-4173938
The Indian Electronic Waybill setting no longer displays an Enterprise-only prompt when it is available in the Community edition. This prevents confusion and allows Community users to install and use the module as expected.
Original PR description
**[FIX] l10n_in: Remove Enterprise Widget from Indian Electronic Waybill** **Description of the issue/feature this PR addresses:** System shows Enterprise Widget on Indian Electronic Waybill module. Although Indian Electronic Waybill is available in community addons . **Impacted versions:** * 17.0 * 18.0 **Steps to Reproduce :** - Install l10n_in module. - Now Go to the invoicing --> Configuration --> Setting. - See the Enterprise Widget is on Indian Electronic Waybill. **Current behaviour before PR:** Enterprise Widget Should not show on Indian Electronic Waybill as it is available in community addons. **Desired behaviour after PR is merged:** After this PR merge, System will allow to install Indian Electronic Waybill module in community version. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
A small typo was fixed in the web search code, changing an incorrectly spelled internal name to the intended wording. This helps keep the code clearer and reduces the chance of confusion for future maintenance, with no expected change for end users.
Original PR description
typo fix: getContextGroubBy -> getContextGroupBy --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes a display issue in the employee timesheet leaderboard. Previously, the target value wasn't correctly reflected when changing billing time targets. This change ensures that the leaderboard accurately shows the employee's progress against their set billing time target, improving reporting accuracy.
Original PR description
- 17.0 ### Steps to reproduce: - Install sale_timesheet_enterprise. - Select Billing Rate Target and then Billing Rate Leaderboard in settings. - Click on 'Set employee billing time targets'. - Open Mitchell Admin form view and set the value of the Billing Time Target to 150 in the HR Setting tab. - Open 'my timesheet'. - Open the leaderboard, on the right-hand side. - Notice that 'x/150' is displayed for Mitchell admin. - Open Mitchell Admin employee form view. - Set the value of the Billing Time Target to 100. - Again open the leaderboard in the timesheet. ### Issue 'x/' is displayed without the new target value. ### Cause Due to the wrong regular expression for the value. ### Solution Correct the regular expression. task-3970348
This update streamlines the process of booking appointments by standardizing how phone numbers and email addresses are handled. Previously inconsistent usage has been corrected, leading to a more reliable and user-friendly experience for customers. This change improves data accuracy and simplifies the booking flow.
Original PR description
Harmonize 'phone' field, normalize email usage Task-4154838
This fix prevents users from accidentally clicking the 'Pair' button multiple times when connecting an IoT device. After a valid pairing code is submitted, the button is now disabled to avoid errors that occur when the same code is reused. This improves the user experience by preventing confusing error messages during the device setup process.
Original PR description
If we receive a valid pairing code, block the 'Pair' button, since if it is pressed again it will show an error as the pairing code has already been used. task-4207295
This update corrects a test in the SEPA credit transfer module that was attempting to directly modify a protected field. The fix ensures the test follows proper data handling procedures, maintaining the integrity of account number validation in SEPA payment processing.
Original PR description
Direct update sanitized_acc_number is not allowed.
Remove Dependency on hr_contract model as it does exist in the dependent apps for base_automation which would allow tests to fail if the module was not installed. To solve this, the test was compared against a base field instead. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#183573
Original PR description
Remove Dependency on hr_contract model as it does exist in the dependent apps for base_automation which would allow tests to fail if the module was not installed. To solve this, the test was compared against a base field instead. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#183573
Description of the issue/feature this PR addresses: It is necessary to be able to select document type "60 CUENTAS DE VENTA Y LIQUIDO PRODUCTO A" in an invoice or refund. Current behavior before PR: User is not able to select document types "60 CUENTAS DE VENTA Y LIQUIDO PRODUCTO A" in an invoice or refund. Desired behavior after PR is merged: User is able to select document types "60 CUENTAS DE VENTA Y LIQUIDO PRODUCTO A" in an invoice or refund. Task Adhoc side: 40557 Tas
Original PR description
Description of the issue/feature this PR addresses:
It is necessary to be able to select document type "60 CUENTAS DE VENTA Y LIQUIDO PRODUCTO A" in an invoice or refund.
Current behavior before PR:
User is not able to select document types "60 CUENTAS DE VENTA Y LIQUIDO PRODUCTO A" in an invoice or refund.
Desired behavior after PR is merged:
User is able to select document types "60 CUENTAS DE VENTA Y LIQUIDO PRODUCTO A" in an invoice or refund.
Task Adhoc side: 40557
Task latam: 1254
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#176858Steps to reproduce the bug: - In website dit mode. - Click on the footer. - Enable the "Scroll Top Button" option for the footer. - Disable the "Copyright" option for the footer. - Bug: There is a white space below the footer. task-4208475 Forward-Port-Of: odoo/odoo#183514
Original PR description
Steps to reproduce the bug: - In website dit mode. - Click on the footer. - Enable the "Scroll Top Button" option for the footer. - Disable the "Copyright" option for the footer. - Bug: There is a white space below the footer. task-4208475 Forward-Port-Of: odoo/odoo#183514
Issue: The `.o_default_snippet_text` class was not being removed when applying formatting (e.g., bold, italic, font-size) to a portion of the default text in an editable snippet. Steps to reproduce: 1. Insert a snippet with default placeholder text containing the `.o_default_snippet_text` class. E.g. A Banner. 2. Select part of the placeholder text (not the entire text). E.g. "Easily" in the "Banner" snippet 3. Apply a formatting command (bold, italic, font-size change). 4. The formatti
Original PR description
Issue: The `.o_default_snippet_text` class was not being removed when applying formatting (e.g., bold, italic, font-size) to a portion of the default text in an editable snippet. Steps to reproduce: 1. Insert a snippet with default placeholder text containing the `.o_default_snippet_text` class. E.g. A Banner. 2. Select part of the placeholder text (not the entire text). E.g. "Easily" in the "Banner" snippet 3. Apply a formatting command (bold, italic, font-size change). 4. The formatting is applied, but the `.o_default_snippet_text` class remains on the element. 5. Save and re-edit 6. Click on the title -> The text is entirely selected because it's still treated as a default text. This commit ensures the correct behaviour of this feature. task-4147162 Forward-Port-Of: odoo/odoo#183179
This Error occurs when a user tries to archive multiple journals. Steps to reproduce: - Install the ```account``` module - Go to Invoicing / Configuration / Accounting / Journals. - Select two or more journals and try to archive them. ```ValueError: Expected singleton: account.journal(15, 18)``` An error occurs at [1] because the system attempts to retrieve the id from 'self', which contains multiple records. link [1]:https://github.com/odoo/odoo/blob/1f7debc24bab4e0a7f2ef0d85e5
Original PR description
This Error occurs when a user tries to archive multiple journals. Steps to reproduce: - Install the ```account``` module - Go to Invoicing / Configuration / Accounting / Journals. - Select two or more journals and try to archive them. ```ValueError: Expected singleton: account.journal(15, 18)``` An error occurs at [1] because the system attempts to retrieve the id from 'self', which contains multiple records. link [1]:https://github.com/odoo/odoo/blob/1f7debc24bab4e0a7f2ef0d85e50d9381e1826cd/addons/account/models/account_journal.py#L801 To resolve this issue, Use an ```ids``` instead of an ```id``` to get a multiple records. Sentry-5917175119 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#182043