I have attached the Screen shot and Sail code. Form should not submit when numer

attached the Screenshot and Sail code.

sailcode.txt

You can do form-level validations in the a!formLayout() in order to check the saved value passes numeric validation.

Your SAIL code appears to work as you describe; a value of 0 for local!c or a non-integer value for local!b prevents the form from submitting.

You can check this by looking at the value of ri!cancel when in the interface designer (which is mapped to both buttons); it remains null. Once the value of ri!cancel changes, that's the form submitted.

Whilst it may look like the form is submitting when you click the button as you see the "Loading" notification at the top of the screen, the form won't have submitted until the value of ri!cancel changes.

philb/conorc . Please give first text field in local!b and next text field in local!a and null in local!c then form submits even if numeric validation failed in local!b but it should not. Bottom section will be hidden by giving the value in local!a. Pls assist on this.

This is because, as far as the form is concerned, the two lower fields do not exist if the top field is populated; there's no validation as the fields simply don't exist. What exactly is the use case here?

You have to put the numeric validation in the validations field in the a!formLayout(). That way the validation will always be checked, even if a specific section is hidden.

You'll need to write a rule to check if local!b is a number, usually that's done this way:
ri!variable: the string you'll be performing the numeric validation on.
len(cleanwith(ri!variable,"0123456789"))=len(ri!variable)

Philb - SAIL form does not support section within section. Hence we build the screen attached with multiple richtext link so the user can collapse and un collapse. Each link will call sail form which has multiple section. Issue: if user collapse and submit then form submit even if numeric validation fails but user expects not to submit the form and populates error message that numerica validation fail.

conorc is right - you can write form-level validation for this and check against the values of local!a, local!b etc.

philb/conorc For Numeric validation, i will make column a!textField from a!integerField and check for formlevel validation as mentioned by conorc. We do have date validation, we cant do the same for date validation as we cant change a!dateField to a!integerField for date.

and also if column field is defined as a!integerField value will not be saved if the numeric validation fails and it will be saved as null.