Daily updates from Odoo
Thursday, January 2, 2025
5 changes
2 changes
Resolved issues and error corrections
IoT Boxes now receive both device-specific and generic handler files when updating. This prevents missing components that could stop connected hardware integrations from working correctly.
Original PR description
In this [PR](https://github.com/odoo/enterprise/pull/75443), we added conditions not to download already up to date handlers. We introduced a condition to only download Windows handlers on Windows and Linux ones on Linux: as some are not plateform-specific, we were not sending them to the IoT Box. The condition is now adapted to download both plateform-specific and generic handlers to IoT Boxes.
This fix prevents an error when staff click the customer button after settling a customer's due account in Point of Sale. It improves checkout reliability and avoids interruptions during customer account payment workflows.
Original PR description
Steps to reproduce : ==== - Open POS - Select customer and pay through the customer account payment option. - Again go to customer and select customer. - Settle the due amount & complete payment. - Click on the customer button. - Traceback appears. Fix : ==== - Fixed improper value parsing to ensure correct behavior. task - 4376767
3 changes
Resolved issues and error corrections
This fix prevents production spreadsheets from blocking copies of older versions when referenced fields or data sources have since changed or been removed. Development and testing environments still keep the validation checks so dashboard issues can be caught before release.
Original PR description
Following #184846, the data validation is no longer necessary in a production context. Moreover, it currently limits some capacities for the user to user the history of the spreadsheets. Eg: - Create…
Following #184846, the data validation is no longer necessary in a production context. Moreover, it currently limits some capacities for the user to user the history of the spreadsheets. Eg: - Create a new field with studio - Add a datasouce in a spreadsheet which relies on that field - make a bunch of revision - Delete the field you created - Go back to the spreadsheet - Open the version history and try to "make a copy" of some recent revision => it will throw as you try to create a spreadsheet with invalid fields However, the data validation still make sense to alert developpers to adapts dashboards when they change the schema of some tables. This revision deactivates the data validation on production which ensures that the last point is still respected while developping (will be detected by runbot tests). Task: 4363803 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The sales product catalog now keeps the discounted pricelist price visible after a product is added to an order. This prevents customers or sales teams from seeing the price jump from the discounted amount back to the original price when using pricelists and discounts.
Original PR description
Steps: - install sale and activate pricelists - activate discounts from setting - create a product with price 100 - create a pricelist with of 2% discount on the product - create a sale order with the new pricelist - open the new product in catalog and add 1 quantity Issue: - the price for the product changes from 98 to 100 after adding quantity Cause: - the display price in catalog comes from either SOL price unit or computed from SO pricelist_id. When discounts setting is active the SOL price_unit is pricelist price without discount else with discount. Hence when first time the catalog is loaded it is computed from SO's pricelist and after adding a quantity it takes pricelist price without discount from SOL Fix: - Updated `_update_order_line_info` so it will always take the pricelist computed price and not SOL unit_price opw - 4345503 opw - 4406373 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Partner Ledger no longer crashes when partner names start with special characters such as '~' and report grouping is enabled. This ensures accounting users can open and review ledgers normally even when customer or vendor names contain unusual characters.
Original PR description
Steps --------- 1. Debug mode 2. Go to Accounting 3. Configuration > Management > Accounting Reports 4. Open "Partner Ledger" 5. In the Options tab, set the "Prefix Groups Threshold to 3" 6. Create 3…
Steps
---------
1. Debug mode
2. Go to Accounting
3. Configuration > Management > Accounting Reports
4. Open "Partner Ledger"
5. In the Options tab, set the "Prefix Groups Threshold to 3"
6. Create 3 different partners, each having their name starting with a '\~'
7. Create an invoice for each of the partners created in previous steps
8. Open the partner ledger -> Traceback
Problem
---------
When there are more lines in the report than the prefix group value, the partners are grouped by names: P -> PA -> PAR, etc.
However, some partners could have a '\~' in their names making the groupby line_id \~account.report\~14|{"groupby_prefix_group": "\~"}\~\~. The line ID being split using the | and \~ characters, it causes some issues.
Solution
---------
Since the line ID format is fixed: markup\~model\~id|markup\~model\~id|... We can split from the back and hard limit the split to 2 to make sure we always have (markup, model and ID) no matter the content of the markup.
task-4420258