Daily updates from Odoo
Friday, October 25, 2024
7 changes
1 change
Enhancements to existing features
Commission purchase orders are now grouped across multiple salespeople when they relate to the same partner, reducing the number of documents created. This lowers processing effort for accounting teams while keeping salespeople able to access the relevant purchase orders.
Original PR description
Previously, commission POs would be grouped per salesperson. In large companies commission is generated through different salespeople which leads to many POs to the same partner. This causes more overhead for the accounting teams on both sides: there are more POs to process on one side, and more invoices to process on the other. To minimize the number of POs, we remove the salesperson from the domain and stop assigning them as user_id (there can now be multiple). To ensure they keep access to the same POs as before, we add them as a follower on the PO and modify the record rule to take this into account. task-4250635
4 changes
Enhancements to existing features
The chatter composer now presents sending guidance and action buttons in a cleaner, more compact layout. This makes writing, sending, and editing messages easier to understand and keeps common actions more visible for users.
Original PR description
- Reword "Ctrl-Enter to send" to "or press Ctrl + Enter" - Show emoji action inline with 1st line of composer textarea - Other actions have been moved in same row as "Send message"/ "Log note", at the very end. Similar change has been made to editing message. Part of task-4260440 https://github.com/odoo/enterprise/pull/72074 <img width="795" alt="Screenshot 2024-10-18 at 12 48 11" src="https://github.com/user-attachments/assets/38d74a0b-3671-49dd-b7c0-cdc5d38b719f"> <img width="354" alt="Screenshot 2024-10-18 at 12 48 42" src="https://github.com/user-attachments/assets/acde081f-805f-4c18-8cc4-a838f4c2646e">
Invoice forms now open much faster on large databases when Indian withholding is installed. The change improves lookup performance for related withholding entries, reducing delays for users working with invoices.
Original PR description
## Description Opening of the form view for invoices is slow on large databases. It's due to the presence of the `l10n_in_withhold_move_ids` in the form view. It's inverse `l10n_in_withholding_ref_move_id` isn't indexed, defaulting to a Seq.Scan on `account.move`. ## Benchmark On next.odoo.com, opening an invoice form view | web_read > read | Before | After | |-----------------|--------|--------| | Timings | 3.35s | 0.02ms | --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Stock deliveries to customers and production now default to being made to order rather than using the previous mixed stock-or-order behavior. This makes replenishment behavior clearer and updates related labels and messages so users better understand how quantities and procurement groups are handled.
Original PR description
This PR introduces a couple of modifications regarding procurement methods, namely - Stock to Customer/Production rules are now using make to order procurement method instead of `mts_else_mto` - `mts_else_mto` message has been modified to better reflect its behavior now task-4150122 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The messaging composer styling has been refined to provide a cleaner and more consistent experience in WhatsApp-related chatter interactions. This helps users write and review messages more comfortably without changing the underlying workflow.
Original PR description
https://github.com/odoo/odoo/pull/183823
2 changes
Enhancements to existing features
This update enhances the performance of the VAT Book report by limiting the number of displayed lines, preventing browser overload. A warning message is now shown if lines are hidden, ensuring users are informed and avoiding unexpected behavior. The change improves report loading times for large datasets.
Original PR description
When this report contained too many lines (~6000), the browser couldn't handle the load and did not manage to render it. This is a known case, which normally only happens with line expansion, for…
When this report contained too many lines (~6000), the browser couldn't handle the load and did not manage to render it. This is a known case, which normally only happens with line expansion, for which the prefix groups and load more features have been made. In this case, though, it's a bit different, as those lines are directly at the root of the report (they don't come from a line expansion). We make the choice here to use the load_more_limit anyway as a means to put a limit to the number of lines that are shown. When this limit is reached, we just don't display the exceeding lines, and replace them by a summary line. To avoid confusion, a warning is now shown on top of the report when some lines need to be hidden. Since such a warning requires a module update (because it's a template, and needs to exist in db), we only apply our new trimming mechanism if the warning template exists (and can hence be displayed). This way, we won't change the behavior on existing databases without being sure the user is properly notified. Plus, thanks to that, we're sure the old load_more_limit value (originally 80 by default) set on the VAT Book will have been increased to a value fitting our use case more, so we won't bother people with excessive trimming. Original fix suggestion raised here by Adhoc: https://github.com/odoo/enterprise/pull/45936 Forward-Port-Of: odoo/enterprise#72096
This update optimizes how Odoo searches for documents, making it faster to find files based on the related model and ID. Similar to how attachments are searched, this change enhances the efficiency of document retrieval, particularly when using complex search criteria. This improves overall user experience and system performance.
Original PR description
Add a compound index on (`res_model`, `res_id`) to support domains searching documents based on those criteria, similarly to `ir_attachment_res_idx` on `ir.attachment`.