Daily updates from Odoo
Monday, March 6, 2023
10 changes · master
Enhancements to existing features
The Chilean SII Partner Activities form now uses a cleaner page layout in Accounting configuration. This makes the screen easier to read and more consistent with other Odoo forms, with no change to business data or workflow.
Original PR description
currently for the form view of the model l10n_cl.company.activities sheet tag is not added. Accounting -> Configuration -> Chilean SII -> SII Partner Activities. adding sheet to the form view for better ui
This update makes several salary and appraisal fields available for translation. It helps companies using multiple languages provide clearer, localized HR information to employees and managers.
Original PR description
https://www.odoo.com/web#id=3159917&menu_id=4720&cids=1&action=333&active_id=1251&model=project.task&view_type=form
Resolved issues and error corrections
Demo forum posts in the Helpdesk Forum area are now assigned to the intended user instead of Odoobot. This keeps demo karma ownership accurate and avoids confusing sample data when teams review or demonstrate the feature.
Original PR description
Purpose ======= Now that we show the owner of the Karma tracking, we want to fix the demo data, so they do not belong to Odoobot. Task-2234179
This fixes a minor issue in the Knowledge app's data setup process that could fail when article member information is missing. The change helps keep setup and test data generation reliable without changing normal user workflows.
Original PR description
We here fix the issue of possibly iterating over a `False` value (`get` fallback) for `article_member_ids` (from c1c275cf) by avoiding the loop altogether in this case, in favor of readability and efficiency. Task-3215864
Code cleanup and technical improvements
This internal cleanup ensures field components use the settings from the exact view element being displayed, rather than accidentally reusing settings from another matching field. This reduces the risk of inconsistent behavior in screens where the same field appears multiple times with different options.
Original PR description
This commit is to replace all uses of activeFields in Field composents by passing fieldInfos to extractProps. We will therefore retrieve the node-dependent information in the extractProps function.
Why?
This ensures that the info used is that of the correct node. Because the activeFields function contains the information from the last node that referred to the same field.
Example:
<tree>
<field name="a"/>
<field name="a" context='{'b':"yop"}'/>
</tree>
For the first field:
FieldInfo.context = {}
activeField.context = {'b':"yop"}
For the second field:
FieldInfo.context = {'b':"yop"}
activeField.context = {'b':"yop"}
Part of task: 3179751This update removes old testing support code that is no longer needed after related areas were moved to the newer interface framework. It should not change day-to-day user workflows, but helps keep the codebase simpler and easier to maintain.
Original PR description
The corresponding codebases have been converted to owl, and those patches are no longer useful.
This update renames an internal label used when working with related fields, making the code easier for Odoo teams to understand and maintain. It does not introduce new functionality or change the user experience, but helps reduce confusion for future development.
Original PR description
[REF] *: rename fieldsToFetch to relatedFields We take advantage of the change of api made in commit https://github.com/odoo/odoo/commit/145540921f2629ae188c84dee17c8d95dccdde16 to rename FieldsToFetch to relatedFields.These two commits are in the same version of odoo (16.2). FieldsToFetch is not a good name for defining the fields to be fetch for relational fields. So we decided to rename it to relatedFields. Part of Task: 3179751
Miscellaneous changes
Sign runs tests with root user which is inactive. However inactive users should never be added as followers, which is now fixed in community. This commit updates tests accordingly. Tests should probably user a real user, but trying to convert them lead to other issues in tests which require some cleaning, and which is outside the scope of this fix. Task-3046371 (Mail: Better Language Support in Composer) Backport of odoo/odoo@c9a0f3e10d179335b397778834c4b1ba34ebd2c2 Forward-Port-Of: od
Original PR description
Sign runs tests with root user which is inactive. However inactive users should never be added as followers, which is now fixed in community. This commit updates tests accordingly. Tests should probably user a real user, but trying to convert them lead to other issues in tests which require some cleaning, and which is outside the scope of this fix. Task-3046371 (Mail: Better Language Support in Composer) Backport of odoo/odoo@c9a0f3e10d179335b397778834c4b1ba34ebd2c2 Forward-Port-Of: odoo/enterprise#37834 Forward-Port-Of: odoo/enterprise#37781
Starting january 2022, Tax Authorities in Norway require tax returns to be submitted online. The easiest way to do so is to submit the tax report in a specified XML format, that needs to be implemented (done here). The current tax report in Odoo is outdated, the following PR addresses this problem: https://github.com/odoo/odoo/pull/84253 Changes: - add XML template for tax return - add XML generation model task id=2667013 Forward-Port-Of: odoo/enterprise#37134 Forward-Port-Of: odoo/
Original PR description
Starting january 2022, Tax Authorities in Norway require tax returns to be submitted online. The easiest way to do so is to submit the tax report in a specified XML format, that needs to be implemented (done here). The current tax report in Odoo is outdated, the following PR addresses this problem: https://github.com/odoo/odoo/pull/84253 Changes: - add XML template for tax return - add XML generation model task id=2667013 Forward-Port-Of: odoo/enterprise#37134 Forward-Port-Of: odoo/enterprise#23041
Currently, SCT requires the journal to be in a set of determined currencies. We want to allow using this payment method for all journals, whatever their currency. The only check that should be made is on the currency of the payment. opw-3159737 Forward-Port-Of: odoo/enterprise#37733
Original PR description
Currently, SCT requires the journal to be in a set of determined currencies. We want to allow using this payment method for all journals, whatever their currency. The only check that should be made is on the currency of the payment. opw-3159737 Forward-Port-Of: odoo/enterprise#37733