Daily updates from Odoo
Tuesday, August 20, 2024
15 changes
1 change
Resolved issues and error corrections
This fixes an issue where saving an inventory receipt could fail after users entered lot numbers in detailed operations. The change prevents receipts from getting out of sync, so users can save and validate tracked products without missing-lot errors.
Original PR description
Steps --- * install stock * create product P, and Q tracked by lot * create a receipt for 1 P and 1 Q > *Mark as Todo* * go to the detailed ops for the P move (list icon on the right of the lines) * set the lot name to 001 > *Save* * repeat for the Q move, set the lot name to 002 * Try to save the picking * => **clicking the cloud save icon does nothing** * Try to Validate * => Traceback: missing lot for the Q move Cause --- We try to save the picking when it is dirty when opening the move lines This will create new datapoints corresponding to the backend data, and but the datapoints linked to the inputs are still the old ones so we become out of sync opw-4107258
4 changes
Resolved issues and error corrections
Screen orientation changes for self-ordering IoT displays are now sent directly from the user interface instead of the server. This avoids connection issues where the backend could not reach the IoT box, helping display rotation changes apply reliably.
Original PR description
As we performed the screen orientation update request from the backend, IoT couldn't be reached. We now send the request from the JS. Community PR: [https://github.com/odoo/odoo/pull/177236](https://github.com/odoo/odoo/pull/177236)
The report editor now avoids a visual overlap between heading hints and displayed field expressions. This makes report editing clearer and reduces confusion when working with dynamic heading content.
Original PR description
Before this commit, when a h2 node has a t-out, there was a collision between the display of `.o-we-hint` and the display of the expression of the `t-out` in terms of styling. This commit solves this by giving priority to the expression.
This fixes an automated test so it waits for all four serial numbers to finish processing before checking results. The change helps prevent false build failures and improves confidence in the stock barcode workflow validation.
Original PR description
In the tour `test_serial_product_packaging`, we didn't wait for the four serial numbers to be fully processed before checking the app state, which can cause race condition (only 3 serial numbers processed when doing the asserts.) runbot build error: [75125](https://runbot.odoo.com/web#id=75125&view_type=form&model=runbot.build.error&menu_id=405&cids=1)
Self-order kiosk setup now connects to IoT devices correctly when the database uses a secure HTTPS connection. This prevents connection errors during kiosk installation and helps keep setup reliable for users.
Original PR description
We were fetching through http, leading to errors when fetching from a https db. Now using `rpc` instead of `fetch` to request dynamically.
10 changes
Resolved issues and error corrections
Fixed an issue where batch payment amounts weren't updating when individual payments within the batch were reconciled with bank statements. The system now properly recalculates the remaining balance of a batch whenever any of its payments are matched, ensuring users see accurate amounts in their bank reconciliation interface.
Original PR description
### Steps to reproduce the issue: 1. Create a Batch of Payments 2. Create a Bank Statement Line and reconcile it with one of the Payments in the Batch 3. Go on any other Bank Statement Line and go to the Batch section 4. The amount shown on the line of the batch did not change ### Explanation: If a Batch is partially reconciled with Bank Statement Lines, `_compute_from_payment_ids_`, which would recalculate `amount_residual`, is not called. ### Fix reasoning: `is_matched` updates on every reconciliation between a Bank Statement Line and a Payment. Adding it to the dependencies of `_compute_from_payment_ids` will make reconciliations trigger the method. opw-4062387 Forward-Port-Of: odoo/enterprise#67519
This update enables customers to generate return labels when using Sendcloud for deliveries, a feature that was previously disabled. A helpful warning message has been added to guide customers when selecting return products. This capability is required by major marketplace partners like Zalando and Otto.
Original PR description
Before this commit: Generating return label on delivery was disabled intentionally. After this commit: Option to select return label on delivery is enabled. A warning is added in `sendcloud_product_selection_widget` for customers befroe selecting return product. opw-4008265
This update fixes the visual styling of appointment descriptions in the Odoo Appointments module. The styling issue has been corrected to ensure appointment details display properly for users booking appointments.
Original PR description
Commit fixes appointment description styling task-3446959
Fixed a bug where cancellation notification emails were only sent when the appointment organizer cancelled, not when attendees cancelled. Now cancellation emails are properly sent to all relevant parties when an appointment is cancelled, ensuring better communication and reducing confusion about appointment status.
Original PR description
**Steps to reproduce** 1).Log as Mitchell, create an appointment, and set Joel as an attendee 2).Log as Joel, open the appointment page, and cancel -> Cancellation mail is not sent **Before this PR** A cancellation email is only sent when the person who books the appointment cancels the appointment. **Technical** https://github.com/odoo/enterprise/commit/46f1b8aaeaa94d3ac7b72784a8fa7120f8a3e8a5#diff-394903898ffdd9f9e1f053ecda2afd00cda86d6cc96159268fbe4fefc62f3a83R187 Before the above commit we were archiving the meeting if there are < 2 attendees in the event. So now we restore that condition with the current conditions **After this PR** Now, a Cancellation email will also be sent if an event contains less than 2 attendee after the cancellation. Task-3975493
This fix prevents duplicate partner records from being created when importing a French FEC file that contains partners already existing in the system. Previously, the system would create a new partner even if one with the same reference already existed, resulting in duplicate contacts. The fix ensures existing partners are properly recognized and reused during the import process.
Original PR description
Steps to reproduce: - Create a partner with a ref "PARTNER01" - Import a FEC with the same partner ref Issue: You will 2 same contacts Cause: During the refactor, the check existing partner has been taken out https://github.com/odoo/enterprise/commit/f60263a105717a7e00b1996b2b2e7b89e514ca54#diff-0c2b1931af025d6a908eea7d818a8858c6e9b03b436757b3c49ffa9857e55ae1L208-L227 Solution: The flow has slightly changed. To make sure the records already existing have an xml_id, we update them opw-3932234
When customers try to purchase items that are no longer in stock, they now see which specific product is unavailable in the error message. Previously, the error didn't identify the product, making it confusing for customers with multiple items in their cart to know what to remove.
Original PR description
__Current behavior before commit:__ When you check out your cart with a product not in the stock anymore you have an error message. There is no product name in this message so if you have multiple products in your cart you don't know which one to remove. __Description of the fix:__ Add the product name in the error message, so it's easy to identify which product to remove of the cart. The warning method is linked to sale.order.line so we can access to the product directly. __Steps to reproduce the issue:__ - add products to your cart - remove one or many products of the stock - try to validate your payment __linked to Odoo PR:__ https://github.com/odoo/odoo/pull/174615 opw-4016059 (upgrade issues) Forward-Port-Of: odoo/enterprise#67423
This fix prevents an error that occurred when validating shipments through Sendcloud's Mondial Relay delivery service if the delivery partner address was missing required parent information. The system now provides a clear error message to users instead of crashing, ensuring a smoother delivery workflow.
Original PR description
## Issue: When validating a stock picking, in a Mondial relay delivery, if the partner created for it has no parent_id, the code will raise an error. ## Steps to reproduce: - Create a sendcloud delivery method (mondial relay) - go to website and order a product, go to checkout - pick sendcloud delivery method - select a relay location - go to odoo backend, go the sale order created by the website - click the SO deliveries smart button - change the quantity to the same as demand - click on the delivery address - remove the partner's parent_id - add an email and phone number to the partner and save - go back to the picking page and click validate - a traceback will appear ## Solution: - in the `_prepare_parcel_common_data` method, raise a user error if the SO has `access_point_data` and the partner has no parent_id. OPW-4042529
This fix corrects an issue in the EU OSS tax reporting module where incorrect tax lines were being included in the closing entry. The problem occurred because a model wasn't properly updated to use the new tax report handler, causing the system to include foreign tax entries that should have been filtered out. This ensures that only the correct tax entries appear in your closing reports.
Original PR description
During aea506700d9a3253c02f46f587a3e360a89cce0b, we forgot to adapt the model that was inheriting `account.generic.tax.report.handler` to make it inherit the new `account.tax.report.handler` model. Because of that, we never passed into the `_get_vat_closing_entry_additional_domain` method, leading to wrong lines being included in the closing entry. Steps: - Install l10n_lu and l10n_eu_oss_reports - Create and confirm two invoices, one with tax 17% S and the other with tax 20.0% FR VAT - Go to LU Tax Report, select the same month as the invoices - Click on Closing Entry button -> There are lines from tax 20.0% FR VAT, they should not be there opw-4015752
When duplicating a pricelist, the system now properly copies time-based rules for rentals and subscriptions, not just regular price rules. This ensures that all pricing configurations are preserved when creating a copy of an existing pricelist.
Original PR description
Duplicating a pricelist would copy over the price rules, but not the time-based rules. Adding copy to this field allows that to work. opw-4088788 Forward-Port-Of: odoo/enterprise#68066
This update corrects the Spanish translation for "Colony code" in the Mexican EDI module from "Código postal" (postal code) to "Código de colonia" (colony code). This ensures accurate terminology for Mexican users when processing electronic invoices, improving clarity and compliance with local standards.
Original PR description
"Colony code" translation changed from: "Código postal" => "Código de colonia"