Tuesday, October 15, 2024
6 changes · 18.0
Enhancements to existing features
The portal now checks that a selected state or province matches the chosen country and requires it when the country’s rules make it mandatory. This helps prevent incorrect or manipulated address data from being submitted, improving data quality and reducing downstream errors.
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
The portal now checks that a selected state or province matches the chosen country and requires it when the country rules say it is mandatory. This helps prevent incorrect or manipulated address data from being submitted, improving data quality and reducing downstream errors.
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
Users can no longer manually create, update, or delete analytic items that are tied to journal items. This keeps analytic reporting aligned with the journal item's analytic distribution and prevents mismatched accounting data.
Original PR description
The analytic items related to a journal item are generated from the journal item's analytic distribution. But it is possible for a user, by accessing the analytic items view, to create/updtate/delete analytic items related to a journal item. The analytic distribution is then unsynced with the analytic items. With this commit, it is no longer possible, so the analytic items of a journal item will always reflect its analytic distribution. task-3977961
Accounting reports can now group results by account code, making financial information easier to review and compare. This supports clearer reporting for businesses that rely on account-code based analysis.
Original PR description
PoC for TSB.
Resolved issues and error corrections
This update resolves several operational issues across Odoo, including Finnish VAT reporting, manufacturing work order quantities and durations, purchase valuation rounding, POS superuser access, image thumbnails, and editor toolbar behavior. These fixes improve reporting accuracy, reduce accounting corrections, and make day-to-day workflows more reliable for users.
Original PR description
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
The self-order payment page now starts the payment process only after the page is mounted, avoiding repeated page renders. This prevents duplicate Razorpay terminal requests for the same order, reducing payment errors and improving checkout reliability.
Original PR description
Before this commit: =================== The payment page was being rendered multiple times due to the `onWillStart` method triggering the `startPayment` method multiple times. This led to multiple requests being sent to the Razorpay terminal for the same order. After this commit: ================== Replaced `onWillStart` with `onMounted` to initiate the `startPayment` method. This prevents duplicate requests to the Razorpay terminal for the same order, ensuring the payment process is handled efficiently. Task- 4254682