Friday, March 7, 2025
4 changes · master
Resolved issues and error corrections
A recent internal change missed a related adjustment in the India reporting module, which could cause errors when using certain linked record fields with avatars. This fix restores the expected behavior so users can continue working in India reports without that disruption.
Original PR description
In the commit [1], we refactor the many2one widgets but the specialisation in this module was missed and caused an error. [1]: bcaa9e9b23d637edfe05baff83aea2ac18d9f4b2
Activating developer mode with the India reports module installed no longer triggers a validation error. This helps administrators and support teams use debug tools without being blocked by an unexpected issue.
Original PR description
This PR fixes an issue where activating developer mode triggers a validation error due to an invalid `component` object. Steps:- 1. Install the `l10n_in_reports` module. 2. Enable debug mode. 3. Receives a validation error.
Manual runs of the reconciliation process now record automated follow-up actions as performed by Odoobot instead of the person who clicked the button. This keeps invoice and activity history consistent with background reconciliation runs and avoids misleading user attribution.
Original PR description
The aim of this commit is to make all the action triggered by clicking the "Run manually" button in the reconcile.model from view performed by Odoobot. Motivation: - information consistency: As this…
The aim of this commit is to make all the action triggered by clicking the "Run manually" button in the reconcile.model from view performed by Odoobot. Motivation: - information consistency: As this is just a button triggering a bunch of automated action, we don't want the user clicking on the button to be tagged in the chatter as performing ALL the side effect action. For example, if an invoice gets reconciled by the process, before this commit, the invoice would be marked as paid by the user that clicked the button. After this commit, it will be marked as performed by Odoobot. - behavior consistency: The end of the method triggers a CRON that will perform this action again on the remaining statement line to process but in the background. This will use the Odoobot user instead of the user that clicked the button. For example, before this commit, an invoice auto-reconciled in the second run of the method will be marked as paid by Odoobot while the invoices autoreconciled in the first run were mark as paid by the user clicking the button. task-id: None (This was brought up during investigation on 4393854)
Clicking a cell in payroll payslip pivot reports no longer triggers an error. This keeps payroll reporting usable by preventing the system from sending users to the wrong payroll screen.
Original PR description
Issue: when clicked on any pivot cell it raise error Solve: remove the js_class as it was forcing the redirect into hr.payroll Task: 4626207