[16.0][FIX]pos_partner_birthdate : #1479
Draft
+10
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
A technical issue was identified in the POS customer creation/edition screen when handling the birthdate field. If a user accidentally selects a birthdate and subsequently clears the field, the system attempts to save an invalid value.
Due to the way the HTML5 date input behaves in the POS, clearing the field results in an empty string (" ") being stored in the component's state. When this value is sent to the server, it triggers a database integrity error because an empty string is not a valid format for a PostgreSQL DATE type.
Cases Covered with This Improvement
This update introduces two fixes to ensure a smooth and error-free customer management flow:
Implemented Solution
This issue was resolved by overriding the
saveChangesmethod in thePartnerDetailsEditcomponent withinClientDetailsEdit.esm.js.FL-571-7738