Tuesday, March 24, 2026
6 changes · 17.0
Resolved issues and error corrections
This update resolves an issue where fields weren't being created correctly within Odoo. Specifically, the system now accurately passes the correct model information during the creation process for certain fields. This ensures data is properly associated and prevents potential errors or inconsistencies in reporting and workflows.
Original PR description
See https://github.com/odoo/odoo/pull/199647.
This update corrects a bug where the canteen cost was incorrectly calculated for employees with no attendance during a payslip. The fix ensures that canteen costs are only applied when the employee has recorded actual working hours. This prevents incorrect charges and ensures payroll accuracy for Belgian employees.
Original PR description
[FIX] l10n_be_payroll: fix canteen cost computation
Bug reproduction: belgium company -> create a new employee -> new contract (payroll wage > 0) -> canteen_cost = 50 -> create payslip -> allocate time off for full month (such that there will be no attendance) -> recompute payslip -> still canteen cost is calculated
Bug cause:
1 - If l10n_be_canteen_cost is > 0 it was computing the canteen cost line for sure
2 - If result_rules['BASIC']['total'] is > 0 then the canteen cost was 50.
Bug solution:
1 - I add worked_days['WORK100'].amount != 0 to the computation condition.
2 - If there is any earned money from attendance or working in that payslip duration, the canteen cost should be deducted completely
3 - If the employee is absent during the payslip, the employee should not pay the canteen cost.
task - 6045406This update corrects an issue preventing the export of Profit & Loss reports with footnotes enabled in the l10n_lu_reports module. The fix addresses a dependency on an outdated model, ensuring proper XML generation and report functionality. This resolves a technical problem impacting report generation.
Original PR description
**Steps to reproduce:** * Install the **l10n_lu_reports** module. * Go to **Accounting → Reporting → Profit & Loss**. * Add a footnote on a report line (**⋮ → Annotate**). * Click **Export (XML)** to open the export wizard. * Enable **Import notes as references** and export. **Observed behavior:** * Export fails with `KeyError: 'account.report.manager'`. * XML file cannot be generated when references are enabled. **Cause:** * The export logic relied on the deprecated `account.report.manager` model. * This model was removed in v17([commit](https://github.com/odoo/enterprise/pull/33604/changes#diff-5fc5051f5c0211c0eec96b892e7d29e01b68d804417443502d17bccd8333d7ecL41)) and replaced by `account.report.footnote`. * The footnote retrieval code was not migrated accordingly. **Fix:** * Migrate reference retrieval to use `account.report.footnote`. opw-5890630
This update addresses a potential issue where the data merge process would fail without warning. Now, if the merge takes too long, a warning notification is displayed, suggesting users reduce the number of records being merged and reloading the model upon successful completion. This enhances the reliability of data operations.
Original PR description
Display a warning notification when the merge operation times out instead of failing silently. Suggest merging fewer records and reload the model on success. task-5912855
This update fixes a potential issue where a user could indirectly change an employee's work email through contract settings. Now, if an employee is linked to a user, their work email will remain unchanged during contract updates, ensuring data integrity. This prevents unintended email modifications.
Original PR description
Due to https://github.com/odoo/enterprise/pull/106974,the employee's work_email may be reset to False when creating or updating an offer. This behavior is acceptable if the employee does not have a linked user. However, if the employee is linked to a user, resetting work_email can allow a user to indirectly modify their own work_email through salary confi. To prevent this, we now ensure that work_email never changes if employee has a user linked to it. ### Steps to reproduce: - Hire an applicant from Recruitment (the employee has no work_email). - Set a random work_email and create a user for the employee. - Open the hired applicant and create a new offer to update the contract. - work_email should not be modified, even after new contract. task: 6033382 Forward-Port-Of: odoo/enterprise#110808
This update fixes an issue where Odoo incorrectly reset the model setting when creating fields for new models. Previously, if a model wasn't fully loaded, attempting to set both the model and its ID would result in the model setting being cleared. This change ensures that the model setting is only set once, preventing errors and ensuring proper field creation.
Original PR description
Why setting `model` again in vals when already is set? Let's avoid this. When this matters? When there is a row in `ir_model` table which is not loaded yet into the enviroment registry list of models. Suppose you want to create a field for that model, and when you do it, filling both model and model_id, and without this fix, the code sets `model = False`, which is not desired. Enterprise https://github.com/odoo/enterprise/pull/109725. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr