Thursday, March 7, 2024
6 changes · saas-17.1
Resolved issues and error corrections
This update ensures that when a manufactured order (MO) is created from a sales order (SO), the analytic account specified on the SO is automatically applied to the MO if no analytic account is defined in the product's manufacturing bill of materials (BOM). This resolves an issue where analytic accounts weren't being correctly transferred, improving financial reporting accuracy.
Original PR description
Steps to reproduce: - Enable MTO - Create a manufactured product (no analytic distribution on the bom) - Create an SO for that product and set an analytic account on it - Confirm the SO Bug: no analytic account on the created MO Fix: inherit MO analytic account from SO if none is set on the BOM opw-3708134 Forward-Port-Of: odoo/odoo#156535 Forward-Port-Of: odoo/odoo#154354
This update fixes a display issue in the Amounts to Settle report, replacing a confusing 'Display Name' column with the more useful 'Name' column. It also adds a search option for journal entries, making it easier to find relevant transactions. This improves the clarity and usability of key financial reporting tools.
Original PR description
This commit fixes the amounts to settle view which currently shows a "Display Name" column which makes no sense and is missing a search option for journal entries. --- enterprise: https://github.com/odoo/enterprise/pull/54137 task-3640027 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#148476
This update fixes a recurring issue where payments were incorrectly canceled due to lingering inactivity timeouts. By explicitly clearing these timeouts before initiating new payments, we've eliminated this error and ensured smoother payment processing for our customers. This improves the reliability of the point-of-sale system.
Original PR description
Before this commit ================== In certain scenarios, when a new subsequent payment was initiated after the initial payment was completed, an error message appeared stating, **Payment is canceled due to inactivity** Issue ===== Failing to remove the previous inactivity timeout before establishing a new one led to the aforementioned error. With this commit ================ Explicitly clear previous timeouts before setting a new one to prevent potential conflicts and ensure a clean timeout environment. Forward-Port-Of: odoo/odoo#156430
This update fixes an issue where the forecast report incorrectly marked stock reservations as 'Reserved from stock' when transfers involved multiple warehouses. Previously, a move could be marked as reserved even if the transfer chain wasn't fully completed across warehouses. Now, the system ensures reservations are linked to the correct transfer, providing accurate stock visibility in multi-warehouse operations.
Original PR description
Commit c05815ae6b8bd will go through a chain a move to set the last one as "reserved from stock" if the first one is reserved even if the cahin is not completed yet. The issue is if the chain is…
Commit c05815ae6b8bd will go through a chain a move to set the last one as "reserved from stock" if the first one is reserved even if the cahin is not completed yet. The issue is if the chain is inter warehouses, a move out in a warehouse can be marked as "reserved" while the stock being reserved is actually the one of another warehouse. ### To reproduce 1. Create 2 warehouses 2. Create a stock rule (pull) and a route between the 2 stock location of those product create a product having the route MTO and the new replenish route create a delivery in the second warehouse. 3. A transfer from the two warehouse should be created and linked to the delivery Open the forecast report for the warehouse that deliver the product -> the delivery is marked as "Reserved from stock" instead of being linked to the replenish transfer. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#152922 Forward-Port-Of: odoo/odoo#152322
This update addresses a recent issue where restricted editor data was unintentionally shared with public users. This commit includes a new test to confirm that the fix implemented in a previous pull request remains in place, preventing future data leakage. This ensures data security and proper functionality for users.
Original PR description
This commit is a follow-up on [1] which fixed the caching of restricted editor which was accidentally shared with public users. It introduces a test that verifies that this fix is not lost. [1]: https://github.com/odoo/odoo/commit/821888023db462d522c5d6de84fcab80a81c2713 task-3482439 Forward-Port-Of: odoo/odoo#156479
This update fixes a warning message that prevented users from submitting expense reports. The system was incorrectly checking all applicability rules without considering the company setting, leading to errors. Now, the system accurately applies company-specific rules for analytic distributions, ensuring reports can be processed correctly.
Original PR description
Have company A and company B With company B: - Create an analytic plan with default applicability 'Mandatory' - Add an applicability: domain 'Expense', applicability 'Mandatory' With company A: - Open the same analytic plan - Set default applicability 'Optional', no assigned applicability - Add an analytc account for the plan - Create an expense, add amount - Create report > Submit to Mananger > Approve Issue: Action will be blocked by Warning message "One or more lines require a 100% analytic distribution." This occurs because the system checks all applicabilities of the plan without taking into account the company opw-3709374 Forward-Port-Of: odoo/odoo#155195