Monday, February 26, 2024
3 changes · saas-17.1
Resolved issues and error corrections
This update fixes a reporting issue where the BoM overview only showed stock in the subcontracting location. Now, warehouse stock is also included in the calculations for free quantity and on-hand quantity, providing a more accurate view of available materials. This ensures better production planning and inventory management for subcontracted products.
Original PR description
### Current behavior before PR In BoM overview report, the free quantity and the on hand quantity only reflected the available stock in subcontracting location ### Desired behavior after PR is merged - Selected warehouse stock is also included in the calculation. - The free to produce quantity was calculated based on the available stock in the warehouse in addition to the subcontracting location. For this reason, `free_to_manufacture_qty` variable was introduced. If it is a non-subcontracting BoM, it will be equal to the free quantity available in warehouse stock. Otherwise, it will contain only the stock in the subcontracting location. **task-3632211** --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#145889
This update fixes an issue where loyalty reward descriptions weren't being translated into the customer's language. Now, the 'Discount' label and all other text within loyalty program descriptions will be displayed in the customer's preferred language, ensuring a consistent and localized experience for users.
Original PR description
Current Behavior: - The word "Discount" is translated in the users language unlike the content of the description which is translated into the customer's language Expected behavior: - The word…
Current Behavior: - The word "Discount" is translated in the users language unlike the content of the description which is translated into the customer's language Expected behavior: - The word "Discount" should be translated as the content of the description. Steps to reproduce: - Sales > Product > Discount & Loyalty Create a new loyalty program and add a translation to the reward description. Create a SO for a customer with the same language. Add products to meet the requirements of the loyalty program and click on Promotion. A line is created for the reward, but the word "Discount" is not translated into the customer's language, but the rest of the description is. Cause of the issue: - The translation of the word Discount is done inside a dictionary comprehension using the _ = GettextAlias() method. As a result, 'self' does not appear in the argument 'frame' from which _ guesses the contextual language. https://github.com/odoo/odoo/blob/4125696a630b3d410f17eab5aa65cc333f4cd9cd/odoo/tools/translate.py#L472-L475 Therefore, the language in which the translation happens is the contextual language of the request (user). Fix: - The translation is applied before the dictionary comprehension so that the method "_" correctly guesses the contextual language. opw-3700429 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#152318
This update corrects a recent change that prevented the creation of customer records for one-time Stripe payments. This was impacting Stripe's fraud detection system (Radar), which relies on customer information. The fix ensures accurate customer data is created, improving payment security and functionality.
Original PR description
Following commit ac90aa07, the Customer object was no longer created on Stripe for one-shot (non-recurring) payments made with Stripe. This prevented Radar (Stripe's fraud detection tool) to work effectively as it could not rely on the customer's name and addresses anymore (see https://docs.stripe.com/radar/integration#recommendations). This commit forces the creation of a Customer object even for one-shot payments. opw-3694379 Forward-Port-Of: odoo/odoo#155179