I have a field (field1) that is pattern enforced. [0-9][0-9][0-9][0-9][.][0-9][0-9][0-9]
If a person enters any value in field1 that is outside the pattern and tries to save the record it fails (as expected). So far so good. If I have a value in another field (field2) that does not match the pattern in field1 and I use a filter set fields action to set the value from field2 to field1 and save, it allows the commit to proceed. NOT expected. Checking to see if anybody else has experienced this or if in my old age I’ve forgotten a rule around set fields that I need to be reminded of…. Tim Powell Remedy Engineer 404-582-5699 (Desk) 704-301-1047 (Mobile)
-- ARSList mailing list [email protected] https://mailman.rrr.se/cgi/listinfo/arslist
