Daily updates from Odoo
Friday, February 7, 2025
14 changes
1 change
Resolved issues and error corrections
Clicking an applicant from the recruitment documents list no longer causes an error. This keeps navigation from job position documents to applicant records working reliably for recruitment users.
Original PR description
Scenario: - install hr_recruitment but not documents (to have the right view) - go to Employee > Configuration > Recruitment | Job Positions - choose a job positions with documents and click on…
Scenario: - install hr_recruitment but not documents (to have the right view) - go to Employee > Configuration > Recruitment | Job Positions - choose a job positions with documents and click on Documents - click on Applicant column on one of the rows => traceback shown: OwlError: Invalid props for component 'FormController': 'resId' is not a number or boolean at Object.validateProps Reason: In saas-17.2 with a7586fdb4123481fd8794ef99fdc372e95de7459 merged in february 2024, many2one_reference was changed from a simple integer to either 0 if unset, or a object containing resId and displayName keys. Fix: Get the id with .resId and this should not happen, but test if the record is set with "if(res_id && ...)" in case res_id was 0. Note: without the fix, the added test fails by opening the view if res_id was 0, and if not the next click would fail with: OwlError: Invalid props for component 'FormController': 'resId' is not a number or boolean opw-4384139 PR note: the test could be run without mails models, but then we would need to mock a lot of models for services (like `mail.ChatHub`) or a method like `prepareRegistry` [from studio](https://github.com/odoo/enterprise/blob/f5b7b53963829b351446e9b6f71e00f21291bc58/web_studio/static/tests/view_editor_tests_utils.js#L123-L153) that would remove all unnecessary services for the test.
2 changes
Resolved issues and error corrections
This fix removes leftover references to a previously removed mobile field in several business workflows. It helps prevent errors or inconsistencies when using delivery integrations and Belgian reporting features after the earlier cleanup.
Original PR description
Missed few places during removal of mobile field See - https://github.com/odoo/enterprise/pull/75203 Task-4555229
The appraisal module’s sample scenario data was updated to match a recent change in how employees are linked to appraisal goals. This prevents setup or automated validation errors and helps ensure appraisal demo data loads correctly.
Original PR description
The commit https://github.com/odoo/enterprise/commit/dd90f66a536539 Changed the `employee_id` field to Many2Many but the change was not reflected in `hr_appraisal_scenario` data. This commit changes the data file to match the new field. Runbot Error: https://runbot.odoo.com/odoo/action-573/115164
11 changes
Resolved issues and error corrections
Users in the Invoicing & Banks role can now access customer statements and partner ledger reports from partner records. This fixes a permissions gap so the new invoicing role can use the expected reporting tools without needing broader accounting access.
Original PR description
With the introduction of Invoicing Enterprise (access to bank recon etc) a new user group was created "Invoicing & Banks" (`group_account_basic`) This group should also be able to access the customer statement / partner ledger (from the partner smart button) Task-4465208
Changing font size on underlined or strikethrough text now applies the sizing to the full styled text rather than only wrapping the inner characters. This keeps the underline or strikethrough visually aligned with the resized text for a more consistent editor experience.
Original PR description
**Problem**: When `u` or `s` tags are applied, changing the `font-size` wraps the text inside these tags instead of applying it to the tags themselves. For example, `a<u>b</u>c` → `a<u><font>b</font></u>c`, which results in an inconsistent appearance. **Solution**: Ensure that the `span` for font size is applied to the highest non-block ancestor to maintain proper styling. **Steps to Reproduce**: 1. Add text. 2. Apply underline. 3. Increase font size. 4. Observe that the underline remains the original size instead of scaling with the text. opw-3086072 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Point of Sale login flow now correctly returns from the screensaver without treating it as the prior screen. This prevents staff from getting stuck seeing the screensaver during employee login after the terminal has been idle.
Original PR description
Before this commit, when the login screen was left idle using an employee login, the screensaver would appear as expected. However, upon user interaction (e.g., moving the mouse), the system would update the previous screen to the screen saver. This causing issues during login where the screensaver would be displayed. opw-4494087 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes how eligible profit and loss accounts are filtered when configuring cash rounding. It ensures the account choices follow the intended rules consistently, reducing the chance of selecting an incorrect account.
Original PR description
The domain on the view overrides the domain on the model. As both domains are correct, this commit moves the partial domain on the view and adds it to the partial domain on the model. task-4514485 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
When Audit Trail is enabled, users who try to delete an incorrect payment now receive a more accurate error message. This avoids suggesting an unavailable archive option and helps users understand why the action is blocked.
Original PR description
**issue:** When "Audit Trail" is activated and a user creates an incorrect payment, deleting the payment is not possible. The error message suggests archiving the payment; however, there is no option to archive it. A more flexible error message should be used instead. opw-4494820
Users in the Invoicing & Banks group can now access customer statements and partner ledger reports from partner records. This fixes missing report access for the newer invoicing role, making day-to-day customer follow-up and account review smoother.
Original PR description
With the introduction of Invoicing Enterprise (access to bank recon etc) a new user group was created "Invoicing & Banks" (`group_account_basic`) This group should also be able to access the customer statement / partner ledger (from the partner smart button) Task-4465208
The commissions report no longer displays a summed Achieved Rate when users group their commission records. This avoids showing an incorrect total for a percentage-based value, making grouped commission views clearer and less misleading.
Original PR description
Steps to reproduce: -Make multiple sales and assign a salesman to it in order to have a commission -Go to My Commissions -Add a Group By -The Achieved Rate column is displaying the sum of the achieved rates instead but it shouldn't display anything Problem: When making a group by on the commissions view and enabling the optional column achieved rate, the result of this group by would be the sum of all the achieved rate for this group, which is not correct. As it was decided that it made no sense, the total would not be displayed anymore. https://github.com/odoo/enterprise/blob/a0215115c13d5e32f1ba3c821f138b188083e76b/sale_commission/report/commission_report.py#L19 Fix: The aggregator parameter was used to prevent the total to be displayed. opw-4512739
This update cleans up an unusual indentation issue in the tax report code. It is a minor maintenance fix that helps keep the reporting module tidy and easier to maintain, with no expected change to business workflows.
Original PR description
The aim of this commit is cleaning a weird indentation introduced by this commit [[1]]. no task id [1]: https://github.com/odoo/enterprise/commit/103369fb171654f4b0457d9b1629224def7465eb
This fixes an issue where old error messages could remain visible after processing Uruguay electronic invoices. Users will see more accurate current status information, reducing confusion when reviewing invoices.
The Kenya payroll accounting demo data now assigns the required payroll journal before confirming demo payslips. This prevents demo installation and automated validation failures, helping test and demonstration environments load reliably.
Original PR description
In odoo 18.0 the `journal_id` on `hr.payroll.structure` [became not required](https://github.com/odoo/enterprise/commit/fb59524a95b0f78112002d1e4d5ad3d6c301de7e#diff-761891fe4e3aa9cb1df74ffca5261004adaf8ac8c3df5857035953e5318be967L16-R16). And in the demo data for this module `action_payslip_done` is called, which [requires](https://github.com/odoo/enterprise/blob/4784d4a48d11c72afb05f2bc7c9062c5644bbf75/hr_payroll_account/models/hr_payslip.py#L53-L54) the payroll structure to have a journal. `hr_payroll_structure_ken_employee_salary` is used as the structure for all the payslips in the demo error in runbot [build](https://runbot.odoo.com/runbot/build/73486292)
The Studio report editor now shows the translation button again when editing a report source. This lets users translate report field labels directly from the editor, restoring expected access for multilingual reports.
Original PR description
Version - 18.0 Problem - The translation button in the studio reports is hidden/ not accessible to the customer Steps to reproduce- Open Sales app > Go to the Studio view > Select Reports from the menu > Open any report among the listed ones On the left hand side - in the studio editor select "Edit Source" On the Edit source file - In the initial version there used to be an EN (Translation button) for them to translate the display field names opw-4417402