implement Front End Data Validation
Customizable validation for data submission forms and update reports and forms would be very nice.
i.e...
0 < DOBmo < 13
0 < DOBday < 32
1900 < vehicleYear < DATEPART(year, now())
FirstName (Not Like "[!((a-z) or (0-9))]")
999,999 < Phone < 10,000,000,000
![](https://secure.gravatar.com/avatar/87615fad0c5e7e1f9c2db73c11917f98?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)
-
Dave commented
100% agree - there are some basics of formatting and validation that would eliminate a TON of custom code (and risk) from my "no code" application. Field masking, formatting and validation - phone numbers, ssn, email, numeric only,
-
Anonymous commented
This should be embarrassing for a Cloud Database company to not have any type of data validation. What if I don't want negative numbers in my number field? Oh, I have to use JavaScript? Sweet, now Caspio Support will refuse to help me because I have JavaScript!
-
Ali commented
its a must for some users.
-
Chad commented
Additionally, custom messages for non-compliance would assist users in understanding why their previous entry was non-compliant.