It would be very helpful to be able to specify a valid date range for a date field to help with avoiding invalid dates being submitted.
For instance, setting a date field to require that the date value is between 1/1/2000 and 12/31/9999.
Also agree. It would be good to be able to validate more in depth the data entered in a field before accepting. For instance, we do assets numbers of a fixed length and numbers only. it would be good to be able to check number of characters entered, digits only etc.
Another wish list item would be to check for duplicates in a loop field. We may have a loop where they enter data for multiple items. it would be good to do a check of all the data entered for duplicates and provide a "Duplicate data" error.
Just some thoughts.. Been a while since I played with numbers fields. Some things might have changed and I could be completely wrong on this..
Numbers only data fields can be used (know this for sure).
The maximum number of characters can also be set. e.g. if you choose 99,999 there cannot be more than 5 digits in the number or the user gets some type of invalid entry warning.
Also, loops can be set to not allow duplicates entries.
If you need to control asset numbers and the asset numbers are pre-determined in your database and are linked to a manufacturer, equipment ID, or model you could use dynamic reference data to limit the asset number selections available to the user.
Hi Keith.
Yes a numbers only can be set, however forgot to mention I also require an exception for "NA" if the asset sticker is missing. I would also want to check the length of the data is in a particular range.
Can you check for duplicates on different iterations of a loop and across multiple fields? For instance, we may want someone to record an asset number for Part A and Part B then repeat that loop x times. Can we still check there are no duplicates in any of the data entered in fields Part A and Part B combined?
Hey Grant,
Numbers can be reference data too.. e.g. your reference data could be N/A, 00001, 00002, 000003.. through 00099. etc or whatever range what you wanted to limit the selections too.. With dynamic reference data, if the user selects Red Widgits, only NA and 00150 to 00200 could be available, Blue widgets, N/A and a different range. Whatever suits your needs.
Preventing duplicates across the table in a loop, I really I don't know how to prevent this. Maybe somebody else (like Sara) knows of a way or work around.
Without knowing the particular situation, I don't know how much more I can elaborate. I do know that with GoCanvas, if there is a will , there's a way. Maybe GoCanvas can custom build something for you.
Good Luck!
Please sign in to leave a comment.
Comments
7 comments