Wednesday, December 18, 2024
17 changes
1 change
Resolved issues and error corrections
Product searches in sales orders now work by product name as well as internal reference. This makes it easier for users to find the right products quickly and reduces search-related friction during order entry.
Original PR description
Version: saas-17.2 Before this fix, the `_name_search` method only supported searching by `default_code`. Issue: It seems to be an issue with product-wise searches in sales orders. Fix: Added `|` operator to the search domain for `name` in `_name_search`. This improves the product search functionality and ensures better user experience when searching for products. opw-4211232
4 changes
Enhancements to existing features
Map views can now open with a predefined grouping, making location-based records easier to organize from the start. The update also adds this option to Studio and prevents crashes when grouping by date and time fields without a selected time scale.
Original PR description
First commit allows usage of the default_group_by attribute in map view. This also makes it included in the map studio sidebar. Second commit fixes a crash which would happen when the user sets a datetime groupBy without specifying the subgroup (scale). It is now set to groupBy month by default in that case. task-4320734
8 changes
Resolved issues and error corrections
This fixes issues in Point of Sale where scale readings on the customer-facing display could fail, show outdated net weight, or remain visible after a weighing was cancelled. It helps restaurant and retail staff avoid confusing customers and prevents errors when switching views without an active order.
Original PR description
Since #176062, the customer display is able to mirror the scale measurements. This commit fixes some bugs with this feature: - A traceback when no order is selected (this can happen when returning to the plan view in a restaurant) - The net weight not updating correctly on the customer display - The scale values remaining on the customer display indefinitely if weighing is cancelled opw-4343571, opw-4343559 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
4 changes
Resolved issues and error corrections
This update resolves a bug where deferred tax dates weren't correctly synchronized between invoice and tax lines. The fix ensures that tax line dates are accurately updated when invoice deferred dates are removed, preventing data inconsistencies. This improves the reliability of tax calculations and reporting.
Original PR description
Duplicating tasks or projects no longer automatically carries over the original task dates, helping teams avoid accidental scheduling mistakes. Gantt view copy actions still preserve dates when users explicitly copy an item by dragging it with Ctrl, so intended timeline copies continue to work as expected.
Original PR description
Related: https://github.com/odoo/odoo/pull/185894 task-4295758
Sign requests are now assigned to the contact linked to a user when multiple contacts share the same email. This avoids sending or tracking a signing request against the wrong contact and helps teams keep ownership clearer.
Original PR description
Before this PR: When creating two contacts with a sales email, one linked to a user and the other not, the sign request would always be assigned to the contact with the smallest ID, disregarding user association. After this PR: The assignment of sign requests now checks if the contact (partner) is linked to a user. If a user is associated, the request will be assigned accordingly. task-3971110 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
Product lists and searches have been adjusted so large product catalogs load much faster. This improves day-to-day responsiveness for businesses managing very high volumes of products, without changing the core product workflow.
Original PR description
For performance reasons: - the is_favorite field is moved from the model's _order to the related tree & kanban views - on product.product it is now a stored related to product.template From nim-odoo survey on a database containing more than 1 million products - stored related field & index: improvement in all cases (2500ms => 500 ms) - limit order & adapt views: name search will be fast (~2 ms)
Orders placed at a self-order kiosk and paid at the counter are now sent to the preparation display as soon as they are created. This helps staff see and prepare kiosk orders promptly, reducing missed orders or delays.
Original PR description
*: pos_online_payment_self_order When creating an order from the kiosk and pay it at the counter, it should be sent to PDIS when creating it. opw-4364309
Partner records now use country-specific labels when warning about duplicate tax IDs or company registry numbers, making messages easier to understand. Morocco also gets stricter ICE number validation and duplicate warnings, while Australia and New Zealand receive clearer company registry labels.
Original PR description
* Add custom tax ID and company registry labels for warning messages to partners with the same tax ID/company registry. * Add custom company registry label for AU and NZ * Make sure the ICE number has 15 digits otherwise show an error message. * Move ICE to be below the Tax ID field. task-4226448 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Customers using a website tied to a company branch could hit an access error when adding branch-specific products to their cart. The fix ensures tax filtering can correctly handle company branch relationships, preventing failed cart actions for public or restricted users.
Original PR description
Scenario: - create a company branch, with a website and a product for that branch - add that product to a cart from that website branch with a user that only has that branch in its allowed companies…
Scenario: - create a company branch, with a website and a product for that branch - add that product to a cart from that website branch with a user that only has that branch in its allowed companies (eg. public user) => an AccessError is raised because we can't read "parent_id" of parent company when passing in method account.tax()._filter_taxes_by_company Note: The error doesn't happen if the product is not in the company, because then we will check access rules which will set the parent res.company record in the cache, so no access error happen. Fix: Add sudo in account.tax()._filter_taxes_by_company method. The sudo could be put on company_id argument by the calling method (eg. 4 calls in website_sale) but it's hard to know that sudo is necessary since it works in a lot of case by chance because the res.company records are already in cache. Note: added test fails with odoo.exceptions.AccessError because we try to read "parent_id" of the branch company. opw-4282334
This fixes two issues in the HTML editor: Ctrl-clicking a link now opens it in a new tab, and internal Odoo links now show the correct preview instead of a warning. This makes editing linked content smoother and reduces confusing error messages for users.
Original PR description
**Problem**: 1. `Ctrl+click` on a link in the editor does not open the link in a new tab. 2. Internal links with the format `odoo/<model>/<record_id>` do not display a proper preview. Instead, a…
**Problem**: 1. `Ctrl+click` on a link in the editor does not open the link in a new tab. 2. Internal links with the format `odoo/<model>/<record_id>` do not display a proper preview. Instead, a warning toaster appears: _"Action `<model>` not found, link preview is not available. Please check your URL is correct."_ **Solution**: 1. Implement the same code as version 17.0 to handle `ctrl+click` for opening links in a new tab: https://github.com/odoo/odoo/commit/981290ee9c88ea00440268d2a7b829d3a601a2d2 2. For internal links (`odoo/<model>/<record_id>`), validate the `action_name` as a model name. If valid, treat `action_name` as the model name for the link preview. **Steps to reproduce**: 1. Open the editor. 2. Add a link with the path `odoo/project.task/59`. 3. Try `Ctrl+click`: - **Issue**: The link does not open in a new tab. 4. Observe the warning toaster: _"Action project.task not found, link preview is not available. Please check your URL is correct."_ opw-4353235 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Orders created at a self-order kiosk and paid at the counter are now sent to the preparation display as soon as they are created. This helps kitchen or preparation staff see these orders promptly and reduces the risk of missed or delayed preparation.
Original PR description
When creating an order from the kiosk and pay it at the counter, it should be sent to PDIS when creating it. opw-4364309
The Moroccan reporting export now makes it possible to identify partners that are missing required ICE or Tax ID details when preparing XML reports. This helps users correct partner records more easily and reduces export issues caused by incomplete tax information.
Original PR description
* From OXP feedback, there was no way to view partners with missing ICE/Tax ID when exporting reports as XML. * Fix ICE numbers in tests. task-4226448
Fixes an error that could stop Australian ABA batch payments from being validated. The payment process now uses the correct payment description field, allowing vendor batch payments to proceed normally.
Original PR description
**Steps to reproduce:** - Install l10n_au_aba - Switch to an Australian company (e.g. AU Company) - Configure batch payments according to fiscal localization docs in Odoo (https://www.odoo.com/documentation/18.0/applications/finance/fiscal_localizations/australia.html#aba-files-for-batch-payments) - Configure a bank account for a vendor - Create a bill for that vendor - Confirm the bill - Register a payment with "ABA Credit Transfer" as payment method - Go to the payments list - Select the created payment and create a batch payment - Validate the batch payment **Issue:** A traceback is raised while trying to access "ref" field of "account.payment" model. **Cause:** "ref" field has been replaced by "memo" field in "account.payment" model. opw-4346794 opw-4355394
Steps to reproduce: 1) Via Studio, modify the 'Journal Items' tab to add 'Start date' and 'End date' to the list view 2) Create a purchase tax 3) Create a bill with the tax created in the previous…
Steps to reproduce: 1) Via Studio, modify the 'Journal Items' tab to add 'Start date' and 'End date' to the list view 2) Create a purchase tax 3) Create a bill with the tax created in the previous step 4) Select deferred dates in the future 5) Check the journal items (two lines with deferred dates) 6) Go back to the 'Invoice lines' tab, delete the deferred dates and check the journal items again => one line still present the deferred dates!! Reason: When removing the `deferred_start_date` and the `deferred_end_date` from the invoice line, the newly computed `tax_key` for the tax line(s) will not have the `deferred_start_date` and the `deferred_end_date` fields, by [_get_deferred_tax_key](https://github.com/odoo-dev/enterprise/blob/c2c3a8591b3a5dfa402acb981564e46e0ff4ced9/account_accountant/models/account_move.py#L582). However, since when updating the tax line(s), we merge the old values with the new values (obtained in part from the before mentioned updated key), by this code in [_sync_dynamic_line](https://github.com/odoo/odoo/blob/f3d3e0c612392f1a35b9c131d29b4f3bd70a9d36/addons/account/models/account_move.py#L2599-L2602), and since the new key values of the tax line(s) does not have the `deferred_start_date` and the `deferred_end_date` explicitly set to `False`, and since the old key values have those fields set, merging new values with the old values will keep the old `deferred_start_date` and the `deferred_end_date`, resulting in a mismatch between the deferred dates on the invoice line and the tax lines. Fix: Now, `_get_deferred_tax_key` explicitly set `deferred_start_date` and the `deferred_end_date` to `False` when `tax_repartition_line_id ` is defined, to make sure they override any old `deferred_start_date` and the `deferred_end_date` existing in the old keys. opw-4328465
This update fixes a bug in the Helpdesk app that previously limited the products displayed on tickets to those linked to the customer's sales orders. Now, all products associated with a contact and their parent company will be visible, ensuring a more complete view for support agents. This improvement enhances the accuracy and usability of the Helpdesk system.
Original PR description
Steps to reproduce:
- Install helpdesk_stock and Studio
- Create 3 contacts, 1 company and two child employees
- Create a quotation for each contact with a different product
- Helpdesk app > Create a ticket
- Add the Product ('product_id') field with studio
- (Under 'Existing Fields' search product)
- (View tab > Show invisible elements > Find product field > untick invisible)
The products from contacts linked to the parent company should appear, but only those related to SOs from the contact itself or its parent company are shown (i.e. We should see all 3 products no matter which contact is set as customer).
This is related to https://github.com/odoo/enterprise/pull/73391, which was a step in the right direction but still insufficient. Unlike that fix however this one is relevant up to master.
opw-4285382
Forward-Port-Of: odoo/enterprise#74361This update fixes an issue where inter-company sales and purchase orders didn't automatically assign a fiscal position. The change removes a redundant setting, allowing the system to correctly calculate and apply the appropriate fiscal position when creating these orders. This ensures accurate accounting and reporting for transactions between companies.
Original PR description
When creating a PO/SO with inter-company rules, the related SO/PO has no fiscal position set, unless having one set on the partner. Removing the `fiscal_position_id` from the values dict allows it to be computed directly at the creation of the related SO/PO Steps: - Have 2 companies A and B - Activate inter-company rules and synchronize sale/purchase orders - With A, create a SO for B, confirm - With B, go to PO and select the related PO newy created -> There is no fiscal position opw-4247948 Forward-Port-Of: odoo/enterprise#73392
This update fixes a problem where tax reports generated as PDFs were displaying cropped columns due to limitations in the PDF generation process. The fix removes unnecessary currency display from report headers, ensuring all data from the table view is accurately included in the PDF output. This improves the clarity and completeness of tax reports.
Original PR description
**Issue:** Some tax reports don't display all data. Last columns may be cropped.  **Expected:** The PDF file should contain all data displayed in the Tax Report table view as is. **Steps to reproduce:** - Activate Accounting app; - Install the Argentina localization; - Move to the Argentine company; - Go to `Accounting` > `Reporting` > `Tax Report`; - Change selection to display some lines (or add invoice lines); - Print PDF report. **Cause:** The columns are cropped because of the global width of the report wkhtmltopdf can't handle correctly. **Fix:** Remove useless currencies' display in headers. Backport improvement (https://github.com/odoo/enterprise/commit/5bbdc059045c1a50c8ef1d6f5f8c9cb76d2d85f9).  Ticket link: https://www.odoo.com/odoo/project/967/tasks/4349604 opw-4349604