Friday, February 14, 2025
23 changes · 17.0
Enhancements to existing features
The Turkish Nilvera integration now handles internet connection problems without showing disruptive error traces. This prevents automated upgrade checks and partner creation flows from failing when external connectivity is unavailable.
Original PR description
Previously, if a request in the Nilvera Client failed due to connectivity issues, a traceback was thrown. This behavior caused upgrade CI failures because the internet is blocked and check_nilvera_customer would be triggered for newly created partners. This commit enhances the exception handling for all requests and fixes the upgrade CI issue by silently exiting the function when a connectivity problem is detected. no task ID.
This change adds more detailed logging around print requests and print processing in the hardware drivers module. It helps support teams diagnose printing issues more easily, especially for customers using Windows IoT where the system may not otherwise confirm successful printing.
Original PR description
Following the ticket opw-4523417 there is a lack of logging related to printing in hw_drivers module which makes it difficult to analyse the issued on the client's side, especially on Windows IoT This PR adds 1) some logs upon receiving of a printing request via longpolling route 2) some logs when the methods of printing are being called 3) some logs when these methods have finished their job Since for printing the Odoo database isn't notified of a succeful printing this is very much needed
Task Adhoc side: 44224 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
Original PR description
Task Adhoc side: 44224 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
Resolved issues and error corrections
The Hungarian EDI module setup now skips over deleted default taxes instead of failing or rolling back related setup data. This makes installation more reliable for companies whose Hungarian tax configuration has been customized.
Original PR description
This commit comes as an apology for the horrible code I wrote in PR #166043 in order for the installation of `l10n_hu_edi` to not fail if some of the default Hungarian taxes (defined in `l10n_hu`) had been deleted. Instead of rolling back the loading of the EDI-specific fields if some taxes don't exist, we can just load those fields on the taxes that do exist. Which is a lot cleaner and simpler. Sorry again! task-none
Documentation and clarification updates
This update records LABISO GmbH's corporate contributor license agreement for Odoo. It confirms the company and listed contributors are covered for contributing code, supporting clear legal ownership and compliance.
Original PR description
This pull request includes an update to the `doc/cla/corporate/labiso.md` file. The change adds a new corporate contributor license agreement for LABISO GmbH, including the list of contributors. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
Certain nondeterministic JS tests can be more easily reproducible if the browser CPU is throttled. For example: rd-112019 https://github.com/odoo/odoo/pull/196980 Chrome does allow CPU throttling using the command: https://chromedevtools.github.io/devtools-protocol/tot/Emulation/#method-setCPUThrottlingRate An environment variable can also be used to ease the usage in a given dedicated environment. task-4559442 Forward-Port-Of: odoo/odoo#197007
Original PR description
Certain nondeterministic JS tests can be more easily reproducible if the browser CPU is throttled. For example: rd-112019 https://github.com/odoo/odoo/pull/196980 Chrome does allow CPU throttling using the command: https://chromedevtools.github.io/devtools-protocol/tot/Emulation/#method-setCPUThrottlingRate An environment variable can also be used to ease the usage in a given dedicated environment. task-4559442 Forward-Port-Of: odoo/odoo#197007
Accounting lines with multiple analytic distributions now adjust their height automatically, so the information is no longer cut off. This makes entries easier to read and reduces confusion when reviewing or editing accounting documents.
Original PR description
This commit fix this UI problem: When you are on an account_move view, create a line and input multiple analytic distributions, the line height stay fixed, and it crop the distributions, making the line unreadable. This commit add a variable height on the analytic_distribution field. task-4213064
This change prevents Brazilian Avatax settings from using the same internal identifier as the standard Avatax settings. It ensures the settings page displays correctly even when modules are installed in a different order.
Original PR description
<setting id="avatax_settings" ...> is created by account, to be inherited by account_avatax. Use a unique id here to not break inheriting views in account_avatax. This uses a slightly awkward id because the more logical "l10n_br_avatax_settings" id is already used below. This issue has remained unnoticed because the account_avatax module is usually installed first. As a result, its views have lower database IDs and are applied before others. However, if you install the l10n_br_avatax module first (e.g., in a Belgian database) and then install the account_avatax module later, the l10n_br_avatax settings view will take precedence. This causes the Avatax settings to display incorrectly. opw-4547721
This update adds missing external codes to Swiss payroll company contribution items used in ELM transmission. It helps ensure payroll data is correctly identified and transmitted for Swiss reporting requirements.
Original PR description
… on company parts
Customized HR appraisal notification emails can now safely include fields from the related appraisal record. This prevents errors when confirming appraisals or sending appraisal surveys, helping HR teams keep tailored communications working reliably.
Original PR description
…emplate context if mail_notification_light is customized Steps to reproduce : ---- - customize mail_notification_light template with a field from record (with Studio or with inherited template) - confirm a Hr Appraisal or send a Hr Appraisal Survey Error before this commit : ---- - RPC error odoo.addons.base.models.ir_qweb.QWebException: Error while render the template KeyError: 'record' Template: mail.mail_notification_light Explanation : ---- We add the record in the template context, therefore any field from the record can be called
This update corrects issues in the Swiss payroll ELM transmission workflow after a recent merge. It helps payroll teams use payslip and configuration screens more reliably when preparing Swiss payroll reporting.
Before this commit, the response from the request that obtains the TURN servers from twilio would fail silently. This commit fixes this issue by logging the status code and te content of the response in case of failure. Forward-Port-Of: odoo/odoo#197628
Original PR description
Before this commit, the response from the request that obtains the TURN servers from twilio would fail silently. This commit fixes this issue by logging the status code and te content of the response in case of failure. Forward-Port-Of: odoo/odoo#197628
Since 1 January 2025, the VAT rates in Slovakia have increased from 20% to 23% and from 10% to 19%. This commit adds the new taxes and updates the fiscal position accordingly. task-4502344 Forward-Port-Of: odoo/odoo#194686
Original PR description
Since 1 January 2025, the VAT rates in Slovakia have increased from 20% to 23% and from 10% to 19%. This commit adds the new taxes and updates the fiscal position accordingly. task-4502344 Forward-Port-Of: odoo/odoo#194686
Steps to Reproduce: - Create a batch transfer. - Print the batch transfer report. Problem: The unit of measure is not displayed next to the quantity. Solution: Access the unit of measure from group_uom in uom instead of move_operation. OPW-4476534 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#196497
Original PR description
Steps to Reproduce: - Create a batch transfer. - Print the batch transfer report. Problem: The unit of measure is not displayed next to the quantity. Solution: Access the unit of measure from group_uom in uom instead of move_operation. OPW-4476534 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#196497
Forward-Port-Of: odoo/odoo#197127
Original PR description
Forward-Port-Of: odoo/odoo#197127
--- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#197489
Original PR description
--- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#197489
Task Adhoc side: 44224
Original PR description
Task Adhoc side: 44224
Add more info to the AR EDI XML file: new required tag CondicionIVAReceptorId where we inform the AFIP responsibility code of the partner. LATAM Task 1300 - ADHOC Task 47476 Forward-Port-Of: odoo/enterprise#78934
Original PR description
Add more info to the AR EDI XML file: new required tag CondicionIVAReceptorId where we inform the AFIP responsibility code of the partner. LATAM Task 1300 - ADHOC Task 47476 Forward-Port-Of: odoo/enterprise#78934
This parameter should have been optional from the beginning. We changed it now because it causes problems when trying to use the TestEdi class with other Tests (Example: AR Website Sales) Forward-Port-Of: odoo/enterprise#78014
Original PR description
This parameter should have been optional from the beginning. We changed it now because it causes problems when trying to use the TestEdi class with other Tests (Example: AR Website Sales) Forward-Port-Of: odoo/enterprise#78014
These fields shouldn't have a namespace. Removing them indeed makes the validation with the xsd succeed. We also clean the xml, by removing whitespaces. Forward-Port-Of: odoo/enterprise#79200
Original PR description
These fields shouldn't have a namespace. Removing them indeed makes the validation with the xsd succeed. We also clean the xml, by removing whitespaces. Forward-Port-Of: odoo/enterprise#79200
Steps to reproduce: - create two companies - create two analytic account (no company defined) - create for company B an analytic distribution model with one of the analytic account and define company A as parter - With Company A, create an invoice and on the line use the other analytic account and confirm Issue: The distribution model for Company B will not be used and only the account distribution from the original invoice will be defined on the line Cause: In the _get_distribution
Original PR description
Steps to reproduce: - create two companies - create two analytic account (no company defined) - create for company B an analytic distribution model with one of the analytic account and define company A as parter - With Company A, create an invoice and on the line use the other analytic account and confirm Issue: The distribution model for Company B will not be used and only the account distribution from the original invoice will be defined on the line Cause: In the _get_distribution method, the partner is incorrectly set to Company B, leading to this issue. opw-4414850 Forward-Port-Of: odoo/enterprise#76395
Outgoing emails now contain more message IDs in references to help thread formation. This is notably due to parent_id being the first thread message, hence often technical, and this cause issues in multi odoo communications. This increases a bit query counters when sending emails. Indeed when preparing outgoing emails we now have to search for messages, and check for subtype details, which means additional queries. See community PR for more details. Task-4559249 Forward-Port-Of: odoo/e
Original PR description
Outgoing emails now contain more message IDs in references to help thread formation. This is notably due to parent_id being the first thread message, hence often technical, and this cause issues in multi odoo communications. This increases a bit query counters when sending emails. Indeed when preparing outgoing emails we now have to search for messages, and check for subtype details, which means additional queries. See community PR for more details. Task-4559249 Forward-Port-Of: odoo/enterprise#79048
In commit fb14e5793f924de21755a2b8e72ef9c651c9fb43, a way to handle related company fields was added, however this doesn't take into account the case where a model _inherits from another model, in that case the field is `inherited` and should be treated the same way as a stored field. Steps - Install Sales and Data Cleaning - Be in a multicompany database - Create a deduplication rule for the product variant model. - Add some field in the "Unique ID Field". - Deduplicate -> ** psycopg2.e
Original PR description
In commit fb14e5793f924de21755a2b8e72ef9c651c9fb43, a way to handle related company fields was added, however this doesn't take into account the case where a model _inherits from another model, in that case the field is `inherited` and should be treated the same way as a stored field. Steps - Install Sales and Data Cleaning - Be in a multicompany database - Create a deduplication rule for the product variant model. - Add some field in the "Unique ID Field". - Deduplicate -> ** psycopg2.errors.UndefinedColumn: column product_product__product_tmpl_id.product_tmpl_id does not exist ** opw-4368443 Forward-Port-Of: odoo/enterprise#75190