2 x potential bugs

[1minManager]

When adding a email address under the user section the App allows email addresses with a trailing full stop. So it’s not doing a comprehensive email address syntax check. This behavour occurs in email type columns too.

Also when copying an app, the copy ends up with an identical App name. Surely it would make sense to name this "Copy of "?

[Suvrutt_Gurjar]

1minManager:

App allows email addresses with a trailing full stop. So it’s not doing a comprehensive email address syntax check. This behavour occurs in email type columns too.

One workaround of ensuring it works well in email type column is to use EXTRACTEMAILS() function. The valid_if of the email column can be

ANY(EXTRACTEMAILS([_THIS]))=[_THIS]

This validation will ensure the format entered by the user conforms to the most used email formats. It will certainly check for leading, trailing full stops, and other special characters.

However, you are righ that it will be good if this validation is built in the email column type.

[Steve · Accepted solution]

A trailing period in an email domain is valid, as far as I know. What makes you think it isn’t?

[1minManager]

Ahh the old FQDN. Didn’t think that aplied to email addresses too. But ok, it seems it does.