Daily updates from Odoo
Tuesday, September 24, 2024
7 changes · 17.0
Enhancements to existing features
The carryover target line name in account report popups is now displayed in bold text for better readability. This makes it easier for users to quickly identify which line the carryover amount is associated with when reviewing financial reports.
Original PR description
For readability; so that the name of the line the carryover is made is more distinguishable from the text around it.
Resolved issues and error corrections
Fixed a bug in the Balance Sheet report where auditing a specific company's column would incorrectly display financial data from all companies instead of just the selected one. The issue occurred because the audit function wasn't applying the company filter that should have been enforced. This fix ensures that when users drill down into a company's numbers, they only see transactions from that specific company.
Original PR description
To reproduce the issue: 1. Create a horizontal group, grouping on "Company" field with a domain matching everything 2. Assign that horizontal group to the Balance Sheet 3. With all the companies active in the selector, open the Balance Sheet 4. Enable the horizontal group ; this should display the column groups accordingly 5. Select a line with non-null values in more than one company; click on the amount displayed in one company's column in order to audit it =====> The tree view that opens also displays lines from other companies; not only the one corresponding to the group we're auditing. It's wrong. This is due to the fact the 'forced_domain' key of the options is added to the result of _get_options_domain() only in _query_get(). The audit does not call _query_get(), and hence never uses the forced domain. We fix it by now simply doing everything in _get_options_domain() directly. Forward-Port-Of: odoo/enterprise#70502
This fix corrects a bug where returned items sent to an inter-company transit location were incorrectly counted as received inventory instead of being deducted. When a company returns purchased goods to another company using the inter-company transit location, the received quantity will now properly decrease to zero instead of doubling. This ensures accurate inventory tracking in multi-company setups.
Original PR description
### Steps to reproduce: - Have two companies: COMP1, COMP2 - In the settings Enable Multi-step routes Prior to 17.2: - Inventory > Configuration > Warehouse Management > Locations - Unarchive:…
### Steps to reproduce: - Have two companies: COMP1, COMP2 - In the settings Enable Multi-step routes Prior to 17.2: - Inventory > Configuration > Warehouse Management > Locations - Unarchive: Virtual Locations/Inter-company transit and set is Return Locations - With COMP1: Create and confirm a PO with COMP2 as vendor for 10 units of a storable product - Validate the receipt and return. Select the Virtual Locations/Inter-company transit as return location and validate #### > On the POL the received quantity went from 10 to 20 rather than 0 #### Note: Starting from 17.2, the Inter-company transit location is the default location destination of the return rather than (Partner/Vendor). It also changed its reference to `stock_location_inter_company` so that the fix should be adapted in that version. ### Cause of the Issue: Currently, the qty_received is computed with respect to moves linkes to the POL. However, a move is flagged as a return only if the usage of its destination supplier (dropshipping and subcontracting flow excluded): https://github.com/odoo/odoo/blob/f494496b5142af23ee46ce249a1063f9d6caf403/addons/purchase_stock/models/stock_move.py#L247-L249 and if it is not flagged a return, its quantity is counted positively rather than negatively in the received quantity: https://github.com/odoo/odoo/blob/f494496b5142af23ee46ce249a1063f9d6caf403/addons/purchase_stock/models/purchase.py#L348-L370 opw-4190647 Forward-Port-Of: odoo/enterprise#70376
This fix enables the quick create form to appear when creating new tickets from the Helpdesk kanban view. Previously, clicking the new button would open the full ticket form instead of the streamlined quick create form. This improves the user experience by providing a faster way to create tickets directly from the kanban board.
Original PR description
Currently, even tough the quick_create view are defined in the code base, and defines on the kanban view, the quick create view is not used. Step to reproduce: - Install helpdesk - Open helpdesk app - Open the 'all tickets' or the 'My tickets' view - Select the kanban view - Click on the 'new' button A ticket view form is opened. Expected behavior : the quick create view form should be open in the kanban view. Source of the issue: the 'on_create' attribute is missing in the kanban definition task - 4047630 version 15.0 - master Forward-Port-Of: odoo/enterprise#70417 Forward-Port-Of: odoo/enterprise#66491
This fix resolves a system error that occurred when adding serial-numbered products to rental orders when the Rental Transfers feature was enabled. The issue happened because the system was trying to compare dates with non-date values. This fix ensures the system properly handles both rentable and non-rentable products in rental orders without crashing.
Original PR description
### Steps to reproduce: - In the settings enable: Rental Transfers - Create a storable non-rentable product tracked by Serial Number - Register 1 Serial Number in stock say SN001 - Create a rental…
### Steps to reproduce: - In the settings enable: Rental Transfers - Create a storable non-rentable product tracked by Serial Number - Register 1 Serial Number in stock say SN001 - Create a rental order for 1 unit of your non-rentble product - Add a lot on your rental order line ### > Traceback: `leaving_move_line.move_id.sale_line_id.return_date <= line.reservation_begin TypeError: '<=' not supported between instances of 'datetime.datetime' and 'bool'` ### Cause of the Issue: Since Commit d014bb68d852fa4dac1d994351dc82dcdff7b545 the availability of rentable produtcs tracked by serial number is computed. However, the `_compute_available_reserved_lots` assumes that the rental order lines have a `reservation_begin` to work properly since it compares these with other 'datetime.datetime'. However, these fields are only sets and hence not `False` for rental lines that is for lines with a rentable product in the rental app: https://github.com/odoo/enterprise/blob/c89e3114f1820750b641ea12676944e8db7888d8/sale_renting/models/sale_order_line.py#L25-L30 https://github.com/odoo/enterprise/blob/c89e3114f1820750b641ea12676944e8db7888d8/sale_renting/models/sale_order_line.py#L53-L56 opw-3839116
This fix resolves an issue where currency conversion was not being performed when consolidating Intrastat reports across multiple companies using different currencies. The system now properly applies currency conversion rates when combining financial data from companies with different currency settings, ensuring accurate reporting.
Original PR description
No currency conversion was performed at all when consolidating multiple companies in different currencies. Forward-Port-Of: odoo/enterprise#70168
This update adds a safety check to ensure that accounting report lines have unique identifiers, preventing potential crashes in the reporting interface. The fix strengthens the testing framework to catch duplicate line IDs before they cause problems for users viewing accounting reports.
Original PR description
The aim of this commit is to add an extra security in the test of the reporting framework. Context: Those line_id are used to recognize lines in the framework and also in the frontend by owl as t-key. Those line_id not being unique would result in a crash in the front-end framework (only from 17.0 as OWL is used starting version 17.0 on accounting reports). Before the commit: There isn't any test performed on the line_id property. After the commit: assertLinesValues will make sure that each line_id is unique for the generated data. Back-ports the following commits: - https://github.com/odoo/enterprise/commit/fa3f03d859a35595990f34606c0864f9868e13fc - https://github.com/odoo/enterprise/commit/74000d6d5c8435bcaad93f7baf143abdf8593064 - https://github.com/odoo/enterprise/commit/fed41d1b3042414823345d995eb173f7acb3c6dc Co-authored-by: Brice Bartoletti <bib@odoo.com> task-4063612 Forward-Port-Of: odoo/enterprise#68840