Sunday, September 14, 2025
1 change · saas-18.3
Resolved issues and error corrections
This fix ensures date, datetime, and date range fields can correctly apply a value set by the system, even when it matches the original value. Users will see the intended date after automated updates instead of an outdated typed input, reducing confusion in forms.
Original PR description
This commit allows date (i.e. date, datetime & daterange) fields to apply a value from the props (e.g. coming from an `onchange`), even if that value is the same as the initial one. Before this commit, it was not possible due to the fact that the date service responsible for the reactivity of the field was updating the input in an incorrect order, causing the field to display the 'input' value, and not the one enforced by the props. Task 4978896 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#225841