Friday, February 14, 2025
6 changes · 17.0
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
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.