Wednesday, October 9, 2024
9 changes · 18.0
Enhancements to existing features
The customer portal now checks that the selected state or region matches the chosen country. It also requires a state selection when the selected country needs one, helping prevent incorrect customer address details.
Original PR description
Description of the issue/feature this PR addresses: - Currently, there is no validation ensuring the selected state corresponds to the chosen country, nor checks that enforce a state selection when required by the country. Current behavior before PR: - Users can select a state that doesn't belong to the selected country. - No validation exists to require a state selection when the country mandates it. Desired behavior after PR is merged: - The selected state will be validated to ensure it belongs to the selected country. - A state will be mandatory when the country requires it, and appropriate error messages will be shown when these conditions are not met. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Loan asset groups now open reliably even when they are not linked to any assets or loans. Reversing long-term loan reclassification entries is also much faster, reducing processing time for large loans from minutes to under a minute in typical cases.
Original PR description
See commits Backport of https://github.com/odoo/enterprise/pull/70658
Resolved issues and error corrections
This update fixes an issue that prevented Saudi Arabia and United Arab Emirates invoice reports from being printed. It updates the GCC invoice report to work with the latest tax total structure in Odoo 18, restoring reliable invoice generation for affected businesses.
Original PR description
**Description of the issue/feature this PR addresses:** l10n_gcc_invoice which is used for l10n_sa & l10n_ae had an issue with tax totals which did not allow the reports to be printed in v18. Link to task: [#4231808](https://www.odoo.com/web#model=project.task&id=4231808) **Current behavior before PR:** l10n_sa & l10n_ae cannot be printed due to an error. **Desired behavior after PR is merged:** Fixes the issue with l10n_gcc_invoice by adapting to the new changes for tax_totals in v18. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix lets Odoo 18 IoT boxes accept connection tokens created by Odoo 17 databases. It prevents connection failures during upgrades or mixed-version setups, helping businesses keep existing IoT hardware working without manual token changes.
Original PR description
In v18, a new format was given to the connection token as shown below: v17: `http://1.2.3.4|12345678|aaaa-bbbb-cccc|M123` v18: `http://1.2.3.4?token=12345678&db_uuid=aaaa-bbbb-cccc&enterprise_code=M123` However these formats are not compatible. Currently you cannot connect a v17 database to a v18 IoT box. After this PR both formats are compatible. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Restaurant tables are now marked as available once an order has been fully paid and completed. This prevents tables from incorrectly staying occupied, helping staff reuse tables without manual correction.
Original PR description
Before this commit: ==================== The table remained occupied after the order was completed (payment done) After this commit: =================== Tables are now released once the order is fully completed, ensuring they are available for future use. Task- 4228671
This update fixes several point-of-sale issues that could cause errors when deleting demo orders, prevent customer counts from saving correctly, and make table transfer instructions hard to read on mobile. It improves cashier reliability and usability, especially for restaurants using POS on smaller screens.
Original PR description
pos*: l10n_in_pos, point_of_sale, pos_restaurant This commit solves multiple tracebacks and bugs in the POS. 1. Fix traceback when deleting demo records in POS. When deleting some demo orders in the…
pos*: l10n_in_pos, point_of_sale, pos_restaurant
This commit solves multiple tracebacks and bugs in the POS.
1.
Fix traceback when deleting demo records in POS.
When deleting some demo orders in the POS, a traceback was
raised because the lines of the orders did not had an order
linked to it. This was because they did not have an uuid.
We now have default uuid values for orders, order lines and
pos payments.
2.
Fix customer count not update.
When changing the customer count on an order in the POS, the
customer count was not updated in the backend. This was because
the customer count was not correctly updated in the frontend
leading to a customer count of 0 in the backend.
3.
Fix "Select table to transfer order" not visible on mobile.
When transfering an order in mobile, the text "Select table to
transfer order" was not visible because the text was too big.
We now display "Transferring" when in mobile. We also stop
showing the floating orders tab when transferring an order as it
makes no sense to show it.
Enterprise PR: https://github.com/odoo/enterprise/pull/70357
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis fixes an issue in Odoo Studio that prevented users from creating related fields pointing to one-to-many records. The correction restores expected Studio customization behavior, helping users configure forms and data relationships without workarounds.
Original PR description
Because of odoo/enterprise@aba680d65ae22f829f7e21e85df1dc86995ec460 it was not possible anymore to create related fields to one2many's in studio. It was just a little mistake in the way the in-expression assignation was written task-4150539
Asset groups opened from Assets or Loans now receive safe default counts when linked records are not available. This prevents error screens and lets users continue working with asset and loan records normally.
Original PR description
Currently, multiple tracebacks occur when the user tries to access the asset group through the internal link from the assets and the loans form view. To reproduce these issues: Traceback 1: 1)…
Currently, multiple tracebacks occur when the user tries to access
the asset group through the internal link from the assets and the loans form view.
To reproduce these issues:
Traceback 1:
1) Install Accounting
2) Create a new loans record from Accounting/Loans
3) Create a new asset group and open the group record through an internal link
```
ValueError: Compute method failed to assign account.asset.group(2,).count_linked_assets
```
Traceback 2:
1) Create a new assets record from Accounting/assets
2) Create a new asset group and open the group record through an internal link
```
ValueError: Compute method failed to assign account.asset.group(2,).count_linked_loans
```
When a user creates an asset group record from loans, the `count_linked_asset` value is not assigned.
Conversely, when creating a group from assets, the `count_linked_loan` field remains unassigned.
Both of these fields are compute fields, and the compute methods have failed to assign values,
resulting in the tracebacks mentioned above.
Giving a fallback value will resolve this issue.
sentry-5967765739Fixes improve commission plan behavior when switching a plan from achievement-based rules to target-based rules after returning it to draft. Subscription sales based on monthly recurring revenue should also now appear correctly in the user's commission view, helping sales teams track expected earnings more accurately.
Original PR description
- When you select based on achievement save, then draft again and change it into based on achievement to based on targets - When I try commission plan based on MRR and try to sell sub, I don't see my commission in "my commission"