Daily updates from Odoo
Friday, September 5, 2025
5 changes · master
Resolved issues and error corrections
Article previews now correctly display embedded account reports instead of crashing. This helps users safely preview and generate knowledge articles that include financial report content, while also improving template consistency.
Original PR description
When previewing an article that contains an account report, the preview currently crashes. This happens because the preview generator encounters an unknown `accountReport` block. To render properly, this block must be transformed - specifically, the reference in `data-embedded-props` must be resolved and the Python dictionary must be converted into a JSON object. This PR updates the system to correctly handle `accountReport` blocks during both preview and article generation. It will also refactor the code to reduce code redundancy and support the `articleIndex` block across all templates. Task-4989809
The salary configurator now shows personal information fields in the salary calculator based on whether they affect net salary, rather than where they are positioned on screen. This makes relevant payroll-impacting details visible to users and reduces unnecessary information being sent to the interface.
Original PR description
Purpose: Show the fields in the salary calculator depending on impact_net_salary and not position attribute
previous behavior:
- fields only appear in the salary calculator if the are configured to have position as side panel
(which make them invisible for the user as they appear under the monthly salary in the salary configurator)
- all fields were passed to both the salary configurator and calculator and unnecessary fields were set to be hidden in the frontend
new behavior:
- removed position setting from hr_contract_salary_personal_info
- fields now appear in the salary calculator depending on impact_net_salary attribute
- passes only the fields that are needed to the frontend
(filtering fields now happens in the backend not the frontend)
task id: task-5025318Mexican payroll can now generate payslips for employees who only receive variable income, such as commissions or bonuses, without a fixed base salary. This prevents an error in the employer social security contribution calculation and helps payroll teams process these cases reliably.
Original PR description
BUG An error is raised when trying to generate a payslip for an employee with only variable income (e.g., commissions/bonuses, no fixed base salary) FIX The rule's find_index function needs to return 0 instead of None in case the daily_wage does not fall within any of the measure ranges Task: 4723413
This fix prevents incorrect or negative ISR tax calculations when a Mexican payroll payslip covers dates across two months. The automatic month-end adjustment was removed, and payroll teams can now enter a manual ISR adjustment when needed for accurate payroll results.
Original PR description
Bug: When a payslip is overlapping two months, the ISR can be negative and is not correctly computed. Cause: There is an adjustment made at the end of each month and each year. This works only if the payslip ends on the last day of the month. Fix: We remove the adjustment and add an input for adjusting the ISR manually. Task: 4790249
The Chilean POS receipt now handles missing resolution date information safely, avoiding a crash when validating sales orders. This helps businesses using Chilean localization complete POS transactions even when optional electronic invoicing settings are not configured.
Original PR description
Currently, when having a CL Company an dusing the POS, it is possible to have the POS crash when validating orders. Steps to reproduce: ------------------- * Install l10n_cl_edi_pos * Create a new…
Currently, when having a CL Company an dusing the POS, it is possible to have the POS crash when validating orders. Steps to reproduce: ------------------- * Install l10n_cl_edi_pos * Create a new company * Put Chile as country * Switch to that company * Create a shop and open it * Make a sale, validate order > Observation: POS Crashes Why the fix: ------------ The crash is happening upon trying to render the receipt because `l10n_cl_dte_resolution_date` is undefined. `l10n_cl_dte_resolution_date`is a field that can be found on the company settings only if the field `l10n_cl_dte_service_provider` is set and is required when the later has either `SII` or `SIITEST` as value. For companies in Chile, there is therefore two setups that leads to having `l10n_cl_dte_resolution_date` undefined. Either the service provider is set to demo, which case clients don't need to fill in the resolution date, either the provider is left empty (since not required upon company creation). Since the field can be undefined, we don't render it when it is. opw-5034091 Forward-Port-Of: odoo/enterprise#93185