Wednesday, September 25, 2024
5 changes · saas-17.4
Resolved issues and error corrections
The Point of Sale now loads products that are referenced by draft order lines, even if they were not already included in the initial product list. This prevents loading errors and helps store sessions open smoothly when draft orders contain those products.
Original PR description
Before this commit, draft order line products not loaded into the PoS could cause errors during PoS loading. This fix addresses the issue by ensuring that all products referenced in order lines are loaded into the PoS, preventing such errors. opw-4167214 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The point-of-sale loyalty flow now blocks reward products when a customer does not have enough loyalty points for that specific reward. This prevents incorrect discounts or free items from being applied and keeps loyalty redemptions aligned with program rules.
Original PR description
Before this commit: ========== - Rewards were being applied even when loyalty points were insufficient for the redemption of loyalty rewards. After this commit: ========== - Reward products will not be applied if the customer's loyalty points are Insufficient for the specific reward product. task-4126886 Related PR: https://github.com/odoo/odoo/pull/180972
The point of sale order report now shows every product line correctly when an order is paid with multiple payment methods. This prevents duplicated rows and inflated totals, giving shop managers accurate sales and quantity figures.
Original PR description
Problem: The query generating the report view has several issues: - The ID for the POS order line is set using `MIN(l.id) AS id`, which causes only the first order line for each order to be…
Problem: The query generating the report view has several issues: - The ID for the POS order line is set using `MIN(l.id) AS id`, which causes only the first order line for each order to be displayed, instead of all order lines. - For mapping the `payment_method_id`, the query uses `order_id`, which results in duplicated records. When multiple payment methods are used for a single order (as in the given ticket), the report shows an order line for each payment method. Consequently, all aggregations are multiplied by the number of `payment_method_id` entries for that order. Steps to reproduce: - Open POS. - Add two products with different quantities. - Use two different payment methods during checkout. - Go to the orders report of that shop. - In the list, click on the order you just created. - Notice that many values are incorrectly multiplied by the number of `payment_method_id` entries. opw-4171674 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The tax report now handles missing net values correctly instead of failing when opening the report. This helps accounting users access tax reporting reliably after creating invoices with taxes.
Original PR description
Currently, a traceback is occurring if the net To reproduce this issue: 1) Install accounting 2) Create a confirmed customer invoice with a product and tax 2) Open `Tax report` report from reporting Error:- ``` TypeError: unsupported operand type(s) for /: 'float' and 'str' ``` This error is occurring after the recent changes from the commit https://github.com/odoo/enterprise/pull/68632/commits/f2bf719665dc3d19024d585e95d4913643b12572 We get `net_value` as an empty string from the below line https://github.com/odoo/enterprise/blob/7f3c71f03ff21dbfdda2763862f609445c4c9103/account_reports/models/account_generic_tax_report.py#L969-L970 But here `net_value` is used to calculate the error value, which leads to the above traceback https://github.com/odoo/enterprise/blob/7f3c71f03ff21dbfdda2763862f609445c4c9103/account_reports/models/account_generic_tax_report.py#L1076-L1077 sentry-5842821270
This fix prevents an error when opening the website editor after upgrading older databases that use Website Events and Website Enterprise. It ensures the website editing components load in the correct order, avoiding a crash for users editing their website.
Original PR description
Steps to reproduce: ------------------ 1. Create a fresh database of version 17.0 or earlier. 2. Install website_event and website_enterprise modules. 3. Migrate the database to version saas~17.4. 4.…
Steps to reproduce: ------------------ 1. Create a fresh database of version 17.0 or earlier. 2. Install website_event and website_enterprise modules. 3. Migrate the database to version saas~17.4. 4. Open the website and click on the `Edit` button, Will encounter Traceback Error. Cause: ------ In this [PR](https://github.com/odoo/enterprise/commit/eedf84b093f6c4803f53d7dc0021830c0c7b84cf) there have been changes made using an xpath where the node 'event_upcoming_snippet_hook' is being used. But there exists a view called 'website_event.snippets', where that particular node 'event_upcoming_snippet_hook' is being replaced with some other element/node. >File(FYR): website_enterprise/views/snippets/snippets.xml As the view 'website_event.snippets' has same priority [i.e; 16 default] as the 'website_enterprise.external_snipppets' view, the 'website_event.snippets' is being executed before than 'website_enterprise. external_snippets' which in result, the node 'event_upcoming_snippet_hook' will get replaced first and will not found for the view 'website_enterprise.external_snippets' when it tries to find that node for making changes and causes the error. Note: The view 'website_event.snippets' will have smaller id than the view 'website_enterprise.external_snippets' cause it exists before than 'website_enterprise.external_snippets'. Solution: --------- Reset the priority of view 'website_enterprise.external_snippets' to 15 so that it will get executed first for finding the node and then gets replaced by the other view 'website_event.snippets'.