If you enter an email address into an ’email’ type field in Force.com, it will validate that the value entered is a valid email, and won’t let you save the record with a bad email. But when you are integrating Salesforce with another system, that system may not perform the same level of verification. You often need to import the record into Salesforce regardless of whether the email is valid, but need to be able to handle bad emails so you don’t try and save a record with a bad email address.<\/p>\n
So I always create a static method in a Utility class that I can use to check an email and return a boolean to tell me if the email is valid or not. If not, I can then save the email address to a non-email text field, and flag the record for review by a business user. The method uses a pattern match with a REGEX<\/a> for matching against emails. I have always used the example from this post<\/a>. But if you search for Email and Regex, you’ll find lots of examples. The one below seems to handle most scenarios though.<\/p>\n \/\/ Then instantiate a new Matcher object \"MyMatcher\" if (!MyMatcher.matches()) { Next up, formatting phone numbers from another system…<\/p>\n","protected":false},"excerpt":{"rendered":" If you enter an email address into an ’email’ type field in Force.com, it will validate that the value entered is a valid email, and won’t let you save the record with a bad email. But when you are integrating Salesforce with another system, that system may not perform the same level of verification. You […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[3,8],"tags":[],"class_list":["post-86","post","type-post","status-publish","format-standard","hentry","category-apex","category-utilities"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/www.bridgefarmconsulting.com\/blog\/wp-json\/wp\/v2\/posts\/86","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.bridgefarmconsulting.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bridgefarmconsulting.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bridgefarmconsulting.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bridgefarmconsulting.com\/blog\/wp-json\/wp\/v2\/comments?post=86"}],"version-history":[{"count":9,"href":"https:\/\/www.bridgefarmconsulting.com\/blog\/wp-json\/wp\/v2\/posts\/86\/revisions"}],"predecessor-version":[{"id":117,"href":"https:\/\/www.bridgefarmconsulting.com\/blog\/wp-json\/wp\/v2\/posts\/86\/revisions\/117"}],"wp:attachment":[{"href":"https:\/\/www.bridgefarmconsulting.com\/blog\/wp-json\/wp\/v2\/media?parent=86"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bridgefarmconsulting.com\/blog\/wp-json\/wp\/v2\/categories?post=86"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bridgefarmconsulting.com\/blog\/wp-json\/wp\/v2\/tags?post=86"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\npublic static Boolean checkEmail (String semail) {
\nString InputString = semail;
\nString emailRegex = '([a-zA-Z0-9_\\\\-\\\\.]+)@((\\\\[a-z]{1,3}\\\\.[a-z]{1,3}\\\\.[a-z]{1,3}\\\\.)|(([a-zA-Z0-9\\\\-]+\\\\.)+))([a-zA-Z]{2,4}|[0-9]{1,3})';
\nPattern MyPattern = Pattern.compile(emailRegex);<\/p>\n
\nMatcher MyMatcher = MyPattern.matcher(InputString);<\/p>\n
\nreturn FALSE;
\n}
\nelse {
\nreturn TRUE;
\n}
\n} \/\/end email check
\n<\/code>
\nAnd then in my integration code, a simple check
\n
\nif (UtilitiesDemo.checkEmail (sEmail) ) {
\n\/\/Use email
\n}
\nelse {
\nhandle bad email
\n}
\n<\/code>
\nYou can see a working example here<\/a><\/p>\n