Friday, September 20, 2024
4 changes
1 change
Resolved issues and error corrections
Demo employees in Sales Timesheets are now linked to newly created, dedicated contacts instead of incorrect existing ones. This keeps sample data cleaner and avoids confusion when evaluating employee, timesheet, and sales workflows.
Original PR description
The employees created in the demo data (see https://github.com/odoo/odoo/pull/108795) of sale_timesheet were linked to the wrong partners, we then create new partners dedicated to those new employees. version-17.2 task-3874828 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
3 changes
Resolved issues and error corrections
This fixes when the Viettel e-invoice XML section is shown on invoice forms. Users should now see the correct page when working with replacement invoice information, avoiding confusion or missing details.
Original PR description
* PROPBLEM: In form view we try to use m2o.field_name which is 'l10n_vn_edi_replacement_origin_id.l10n_vn_edi_invoice_number', odoo doesn't support that so it will not work at least in form view * SOLUTION: this commit make the invisible condition more simpler and create a non-store field to fix the issue 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
When a SendCloud contract has no available rates, adding it to a sales order no longer triggers a disruptive popup. Users now see the same message in a red banner, keeping the workflow clearer and less interruptive.
Original PR description
In this PR ================== Some contracts in SendCloud do not have rates. This caused an annoying popup when adding it to the Sales Order. After this PR, the red banner is displayed with the same message instead of the annoying popup when adding it to the Sales Order. Enterprise PR: https://github.com/odoo/enterprise/pull/66976 TaskId: 4012182
This update adds a missing validation rule to the batch payment system to prevent payment method changes that could violate business constraints. While the standard interface already prevents this issue, the fix ensures the constraint is enforced even when records are created or modified through custom views or direct code, protecting data integrity.
Original PR description
payment_method_id is readonly in account.batch.payment's form view when there is at least one payment on the batch. So, it cannot easily be changed in standard in order to break the constraint. It could however happen in custom views or when generating records directly from the code. Forward-Port-Of: odoo/enterprise#70230