Monday, February 17, 2025
5 changes · saas-17.4
Resolved issues and error corrections
The invoice screen now shows the FACe/Factura-e section only when the related company is located in Spain. This avoids confusing or irrelevant Spanish e-invoicing fields for companies in other countries.
Original PR description
We should only show the FACe/Factura-e section on invoice when the related company is located in Spain. opw-4397651 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users can now archive an inherited view from the main view screen without preventing the main record from being saved. This avoids a workflow interruption for administrators managing technical views in Odoo.
Original PR description
Before this commit, when archiving an inheriting view from a main one (via the list and the form), the main record was not savable. This is due to 6f06420e4a9443c52dc0cb427f8f55eb4aecabce which automatically adds missing but useful fields in a view in readonly mode. This commit adds that field manually to be able to save the active field. opw-4534225 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
This fix allows empty view modifier expressions to be treated safely instead of causing validation errors. It helps upgrades to newer Odoo versions proceed smoothly when placeholder expressions exist in custom or existing views.
Original PR description
When the modifier is empty we don't get any error in the fronted. It's just assumed as `False`. Since 6f06420e we have a new mechanism that adds fields to views as long as they are used in an modifier's expression. This unfortunately fails with a syntax error if the expression is empty. OTOH having an empty expression could be useful for development as a placeholder for further changes. The presence of empty expressions causes issues during the upgrade from <17.4 to higher versions. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Embedded actions no longer fail when their filter setting is intentionally left empty. This prevents errors for users opening those embedded actions and keeps the default behavior as an empty filter.
Original PR description
Steps:
- Set domain of an embedded action to false
- this override the default value
- Try to use the embedded action
Actual result:
- Error due to invalid domain
Expected result:
- Embedded action work and use empty domain as default
opw-4529210
opw-4563505This fix prevents incoming payments that require a partner bank account from also requiring that bank account to be approved for outgoing payments. It avoids confusion and payment setup issues for Italian RiBa payments, where money is received rather than sent.
Original PR description
The require_partner_bank_account flag on the payment shouldn't require the allow_out_payment flag on it when the payment type is inbound as it leads to confusion. This generates an issue with the l10n_it_riba RiBa payment method. It requires the bank account, but the money is incoming, not outgoing. Community PR: odoo/odoo#197141 Old Enterprise PR: odoo/enterprise#77901 Task [link](https://www.odoo.com/odoo/project/967/tasks/) task-4497749