Range validation does not work on an integer field in inline edition, in which a numerical range has been defined.
The problem occurs in the inline edition of any numerical field with a defined maximum and/or minimum: Inline edition does not validate that the new value is a value within the range.
However, it works correctly when editing from the edit view.
Expected Behavior
Validation should also be applied in inline edition.
Steps to Reproduce
In Studio, create an integer field, with Min Value 1 and Max Value 15
Add the field to the detail and list view and verify that we can add a value outside the defined range.
Verify that it works correctly in the editing view.
Your Environment
SuiteCRM Version used: 7.14.0
Browser name and version: Chrome Version 118.0.5993.70 (64-bit)
Issue
Range validation does not work on an integer field in inline edition, in which a numerical range has been defined. The problem occurs in the inline edition of any numerical field with a defined maximum and/or minimum: Inline edition does not validate that the new value is a value within the range.
However, it works correctly when editing from the edit view.
Expected Behavior
Validation should also be applied in inline edition.
Steps to Reproduce
Your Environment