Required Textfield in the editable grid validation not working properly

RE: Required Textfield in the editable grid validation not working properly

Harsha Sharma — Thu, 20 Nov 2025 07:38:05 GMT

As per documentation required condition fires when user submits the form. The 2nd row has error due to "validations" , the 2nd last row doesnt have an error because no data is there so "validation" won't act here. The "Required" attribute will be validated on Submit action only.

'Validations' are triggered by data in field, 'Required' is triggered by Submit form action.

RE: Required Textfield in the editable grid validation not working properly

Anitha Dharmalingam — Thu, 20 Nov 2025 07:37:59 GMT

yeah ok Stefan. Can you please help me on this case how can i achieve it. my requirement is if premium has value, but member doesn't have value it should throw a message saying this is required. can you please guide me here

RE: Required Textfield in the editable grid validation not working properly

Stefan Helzle — Thu, 20 Nov 2025 06:56:01 GMT

Keep in mind that validations only trigger if there is a value. Do not use validations to try to make a field required.

RE: Required Textfield in the editable grid validation not working properly

Jesse Knight — Wed, 19 Nov 2025 20:45:10 GMT

Couple of tips to help troubleshoot:

It appears that everything about your data is based upon text rather than numbers, even though the user is supposed to enter a number. Double check that there aren't whitespace characters in the values provided. You might need a trim() call, or better yet, ensure the data model has integers defined for these fields rather than text. You can also avoid the need to validate that a string is a number by using the integerField component, so long as your use case is within integerField limitations.
We need more context to understand why validation on the top row has fired to begin with, which may help us understand why the bottom row did not fire. A screenshot that shows us what the grid looks like when not globally disabled should help us with some additional context.
The text field's required parameter definition already handles what your validation is attempting to handle. To use your custom message with it, simply pass in the requiredMessage parameter.