Saturday, March 22, 2025
6 changes · 18.0
Enhancements to existing features
Search in Knowledge is being adjusted to return more flexible results, making it easier for users to find relevant articles even when their wording is not exact. This should reduce time spent looking for information and improve day-to-day knowledge discovery.
Resolved issues and error corrections
This fixes a Mongolian localization tax setting so purchase VAT that is included in the price is recognized correctly. Businesses using this tax should see more accurate purchase tax handling and price calculations.
Original PR description
Description of the issue/feature this PR addresses: price_include_override corrected for account_tax_purchase_vat1 tax. Current behavior before PR: This tax indicates Purchase with TAX included in price. But current price_include_override value is "" Desired behavior after PR is merged: price_include_override would have "tax_included" value on price_include_override field. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
**Steps to reproduce:** - Install Accounting and l10n_ke_edi_tremol - Switch to a Kenyan company (e.g. KE Company) - Configure USD currency: * Rounding Factor: 0.000100 * Decimal Places: 4 * Rate: 0.007729205731 Unit per KES 129.379400000000 KES per Unit - Create a product with decimal in the price (e.g. 1234.56) - Create an invoice: * Customer: [a Kenyan customer] * Currency: USD * Product: [the created product] * Taxes: 16% - Confirm the invoice - Send the invoice t
Original PR description
**Steps to reproduce:** - Install Accounting and l10n_ke_edi_tremol - Switch to a Kenyan company (e.g. KE Company) - Configure USD currency: * Rounding Factor: 0.000100 * Decimal Places: 4 * Rate:…
**Steps to reproduce:**
- Install Accounting and l10n_ke_edi_tremol
- Switch to a Kenyan company (e.g. KE Company)
- Configure USD currency:
* Rounding Factor: 0.000100
* Decimal Places: 4
* Rate: 0.007729205731 Unit per KES 129.379400000000 KES per Unit
- Create a product with decimal in the price (e.g. 1234.56)
- Create an invoice:
* Customer: [a Kenyan customer]
* Currency: USD
* Product: [the created product]
* Taxes: 16%
- Confirm the invoice
- Send the invoice to fiscal device (It will not be possible without some credentials. However, if a breakpoint is set at the last line ("return" line) of "_l10n_ke_cu_lines_messages" method, the total amount in KSh sent to the fiscal device can be checked.)
**Issue:**
The total amount in KSh sent to the fiscal device is different than the total amount in USD converted to KSh with the used currency rate.
**Cause:**
In the "_l10n_ke_cu_lines_messages" method (the method used to compute the amounts sent to the fiscal device), a rounding is done by forcing the number of decimal to 2 without taking into account the configuration of the currency when computing the price.
opw-4567098
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#202888
Forward-Port-Of: odoo/odoo#202706The HTML editor now handles cases where the document has no active selection, avoiding an error that could interrupt editing. This improves reliability for users working with rich text content.
Original PR description
Before this commit: this.document.getSelection() can return null and causes traceback when accessing anchorNode at preserveSelection After this commit: ensure document selection is not empty --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Description of the issue this commit addresses: When registering a SEPA payment, it is possible to get a UserError telling you to validate therecipient bank account while it is validated. --- Steps to reproduce: 1. Install account. 2. Activate SEPA Credit Transfer (SCT) in the settings. 3. On the Bank journal's settings, input an account number. 4. Make sure the accounts used for the transfer authorize sending money. 5. Create a move in the misc journal with multiple lines and d
Original PR description
Description of the issue this commit addresses: When registering a SEPA payment, it is possible to get a UserError telling you to validate therecipient bank account while it is validated. --- Steps…
Description of the issue this commit addresses: When registering a SEPA payment, it is possible to get a UserError telling you to validate therecipient bank account while it is validated. --- Steps to reproduce: 1. Install account. 2. Activate SEPA Credit Transfer (SCT) in the settings. 3. On the Bank journal's settings, input an account number. 4. Make sure the accounts used for the transfer authorize sending money. 5. Create a move in the misc journal with multiple lines and distinct partners. 6. Post the move. Go in the journal entries. Select it. "Register Payment". 7. Change the Payment Method for SEPA Credit Transfer. "Create Payments". 8. A UserError shows up. --- Desired behavior after this commit is merged: No UserError shows up, the payments are created. --- Note on the fix: The error happened because one of the condition for raising the UserError is a value of a record in a many2one relation which is a stored computed field. As the payment is created with a list of values, the compute method is not triggered and the many2one remains empty while it should not. This fix makes sure the partner_bank_id is only put in the payment values once it has been computed to avoid keeping it false. --- opw-4518374 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#203003 Forward-Port-Of: odoo/odoo#201608
Steps to reproduce: - insert a line chart into a spreadsheet with the horizontal axis being a time axis - ensures a domain is applied such that at least some past data is excluded - open the configuration side panel - check the "Cumulative data" checkbox => the chart doesn't take into account past data. When reloading it works. opw-4646477 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#202841 Forward-Port-Of:
Original PR description
Steps to reproduce: - insert a line chart into a spreadsheet with the horizontal axis being a time axis - ensures a domain is applied such that at least some past data is excluded - open the configuration side panel - check the "Cumulative data" checkbox => the chart doesn't take into account past data. When reloading it works. opw-4646477 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#202841 Forward-Port-Of: odoo/odoo#202746