Daily updates from Odoo
Friday, November 22, 2024
8 changes
4 changes
Enhancements to existing features
Bulk changes to helpdesk tickets and field service tasks now reuse sales order line lookups instead of repeating the same search for each record. This reduces processing time and database load when many records share the same customer or team, making large updates noticeably faster.
Original PR description
Steps to reproduce: ------------------- 1. Install Project, Timesheets, Helpdesk and Sales apps 2. Create many tickets (e.g. 5k) associated with the same helpdesk team 3. Change the project linked to…
Steps to reproduce:
-------------------
1. Install Project, Timesheets, Helpdesk and Sales apps
2. Create many tickets (e.g. 5k) associated with the same helpdesk team
3. Change the project linked to the helpdesk team
4. It should update the SOL of all tickets linked to that team
Other way to reproduce:
1. Install Project, Timesheets, Helpdesk and Sales apps
2. Create many tickets
3. Go to the list view of tickets
4. Update the customer in all those tickets
Fix:
-------------------
The idea is to batch the RPC (search) made by the method "_get_last_sol_of_customer()". Avoiding to do an RPC for each ticket, we can now re-use the computed SOLs as we store them in a dictionary. It particularly improve performance if we compute the sale_line_id of many tickets having similar commercial partners.
Benchmark:
-------------------
- Usecase: Create 5k tickets associated with an helpdesk team, change the project linked to the helpdesk team, it should update the SOL of all those tickets.
- Parameters: In local, run with "--limit-memory-soft=8589934592", "--limit-memory-hard=8589934592".
- Results:
Without optimization: 34 seconds, 30 665 queries
With optimization: 22 seconds, 15 397 queries
related-https://github.com/odoo/odoo/pull/185132
task-4255293Users can now duplicate approval requests directly from the form and list view menu. This makes it faster to create similar requests and reduces repetitive manual entry.
Original PR description
This PR improves the approval request form and list view by adding a `Duplicate` option to the menu. task-3685226
Users can now create and edit Brazil Avatax operation types in Odoo, matching custom setup options available in the Avatax portal. This helps businesses keep their Odoo tax configuration aligned with customer-specific Avatax settings.
Original PR description
We include the default ones Avatax has in their portal. But customers can create custom operation types on the Avatax side and so need to do similar on our side as well. task-4288101
Studio now includes an Actions tab where users can quickly view and create automated server actions for a model. Newly created actions are automatically added to the model's contextual menu, making common workflow automation easier to set up and use.
Original PR description
This commit adds a studio Tab to quickly access and create ir.actions.server objects. Upon creation, created actions are automatically added to the model's contextual menu. task-4268990
4 changes
Enhancements to existing features
Cashiers can now search for products in Point of Sale using their barcode, instead of only relying on product names or other details. This makes checkout faster and reduces confusion when barcode-based searches previously returned no results.
Original PR description
Before this commit, searching with the barcode of a product would not show any results. opw-4330143 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Restaurant point-of-sale orders now remain linked to their original table when tables are merged and later separated. This prevents lost or misplaced orders, making table management more reliable for restaurant staff.
Original PR description
Before this commit: =================== When merging tables, the order from the original table was transferred to the destination table, and the original table's order was deleted. As a result, when tables were unmerged, the original table's order could not be restored. After this commit: ================== When tables are merged and later unmerged, the original table's orders are successfully restored. This ensures that each table retains its initial order even after being merged and unmerged. Task- 4224207
Kitchen preparation cards now show all table numbers involved when restaurant tables are merged, instead of only the destination table. This helps kitchen staff identify orders more clearly and reduces confusion during service.
Original PR description
Before this commit: ================ When tables were merged in the restaurant, the kitchen display only showed the destination table number on the preparation card. After this commit: ================== Now, if tables are merged (e.g., Table 1 & Table 2), the kitchen display will show both table numbers (e.g., 1&2) on the preparation card. This provides better clarity for the kitchen staff by reflecting the merged table arrangement Task- 4224207 Related Community PR: https://github.com/odoo/odoo/pull/183070
Financial report actions that require the main company and all branches are now clickable and show a clear message when the right company selection is missing. This helps users understand what to do instead of assuming a disabled button is a system issue, reducing confusion and support requests.
Original PR description
When you have a company with branches in a database, some reports only make sense when you have the main company with all its branches selected. Currently some report actions (buttons) were disabled if you didn't have your main company and its branches selected, without any information on why the buttons were disabled. This resulted in people creating tickets because they thought something was wrong. This change makes the buttons clickable again, but instead displays a message saying that the user should select the main company and its branches in order to save a sensible report. [task-4260501](https://www.odoo.com/odoo/all-tasks/4260501)