Branch
[FIX] loyalty: default product for reward in multi company Steps to reproduce: ------------------- - being in a multi-company environment; - have one product made that is first in alphabetical order of "Internal Reference" throughout the database (e.g. [AAA]); - make this product specific to one of the companies (set the "Company" field on the product template) - go into a different company within the database (not the one set on this product); - create a new discount & loyalty record, and set the "Program Type" to "Discount Code". Issue: ------ An access rights error occurs. Cause: ------ When creating a `promo_code` program, we use the first product that can be sold in the default reward values. Solution: --------- Take into account the company in the domain that retrieves the default product.
[FIX] point_of_sale: ensuring the correct removal from self.syncingOrders Previously, the code attempted to delete an element using order_id, but ordersToSync is an array of order objects, not order IDs. The fix updates the loop to use order.id instead of order_id, ensuring the correct removal from self.syncingOrders.
[FIX] point_of_sale: remove raise to continue processing other orders on failure Previously, if a PoS order failed during synchronization from the frontend, the entire process stopped due to the raise statement in the except block. This PR removes raise, allowing the system to continue processing the remaining orders even if some fail. Failed orders will still be logged and an activity will be created for later handling. This ensures that valid orders are not affected by individual failures, improving performance and user experience during data synchronization.
[IMP] spreadsheet: include ongoing day in period filters This commit includes the ongoing day in the current period filters. Now the start date (time) of each period filter is the start of next day, and the end date (time) is the end of today. task 3267525 closes odoo/odoo#118326 Related: odoo/enterprise#39641 Signed-off-by: Rémi Rahir (rar) <rar@odoo.com>
[FIX] account_payment: test fails in Odoo CE due to invoice_payment_state mismatch In Odoo CE, the invoice_payment_state is "paid". In Odoo Enterprise, the invoice_payment_state is "in_payment". This causes the test to fail in CE but pass in Enterprise, making the test unreliable when running in an environment without Enterprise. Current behavior before PR Running the test in Odoo CE only → Fails (expects "in_payment", but gets "paid"). Running the test in Odoo CE + Enterprise → Passes. Desired behavior after PR is merged The test should pass in both CE and Enterprise. The test will no longer check the exact value of invoice_payment_state, ensuring it remains valid across both versions. Steps to reproduce Run the test in an Odoo CE-only environment. Observe that it fails due to the unexpected invoice_payment_state value. Run the test in an environment with Enterprise, and see that it passes.