Daily updates from Odoo
Tuesday, May 27, 2025
5 changes · 18.0
Enhancements to existing features
Public holiday imports are now processed in batches, which greatly reduces the time needed when holidays overlap with existing time off or planning entries. This helps HR teams import large holiday calendars much faster, improving from minutes to seconds in the example provided.
Original PR description
Importing new public holidays from an xlsx file can take quite some time at the moment because Odoo has to reclaim past time off if it overlaps with one of the new public holidays. Currently this…
Importing new public holidays from an xlsx file can take quite some time at the moment because Odoo has to reclaim past time off if it overlaps with one of the new public holidays. Currently this whole process is not properly batched. There is a single record creation in `hr_holidays:_reevaluate_leaves` and a single record write in `planning:_compute_allocated_hours`. This commit optimizes the Public Holidays creation by batching the two methods mentioned above. Batching the create call is straightforward. Batching the write might seem useless at first as UPDATE queries are already batched on the ORM level. But actually the performance bottleneck comes from the post-processing done after writing a new `planning_slot.allocated_hours` value. By grouping the slots by allocated_hours we can speed up this post-processing. #### speedup Trying to import 72 new Public Holidays that lead to writing allocated hours on 85 planning slots - 2min -> 4.76s --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Point of Sale now avoids reloading pricelist details that were already fetched earlier. This reduces unnecessary data transfer and helps sessions load faster, especially for businesses with large pricelists.
Original PR description
Before this commit, loading missing pricelist items would also resend the entire pricelist record, even though pricelist records are already loaded at the beginning. This caused unnecessary data transfer and slower performance, especially when pricelists contained many items. opw-4812031 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Invoice and accounting forms now place the cursor in the customer field, or the reference field when customer is unavailable, instead of the document number. This helps prevent accidental edits to accounting sequences and improves form usability when users start typing immediately.
Original PR description
*: account, partner_autocomplete, web --- This PR is a backport of [this PR](https://github.com/odoo/odoo/pull/203522) Some changes have been made to it for retro compatibility while allowing the change in stable. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
When users create a new account move, the cursor now starts in the next editable field instead of the displayed name field. This helps prevent accidental changes to document numbering or sequence information during data entry.
Original PR description
made the default focus to be the next editable field in the form view when people create a new account move the cursor focus on the desplayed name so people tend to mess up the sequence so we changed the focus to the next editable field to not mess up the sequence task-4558713 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Public holiday planning entries are now created more efficiently by grouping similar schedule updates together. This reduces processing time when many planning slots are updated, improving responsiveness for teams managing calendars and holidays.
Original PR description
Related to odoo/odoo#209846