🚀 Workflow Rules vs. Flows: The CONTAINS dilemma
Salesforce veterans might recall how simple life seemed with Workflow Rules when handling comparisons using CONTAINS.
You could just slap in multiple values and call it a day:
• Email CONTAINS "@SpamSender.com,@spammy.net,@spammer.org"
However, the shift to Record-Triggered Flows introduces a wrinkle: this doesn’t work anymore.
Per the Salesforce documentation:
“Passing multiple comma-separated values against the CONTAINS operator in the same condition doesn’t evaluate the Process or Flow as intended.” 🙃
The Result?
Your old but elegant one-liner now turns into:
• Email CONTAINS "@SpamSender.com"
• OR Email CONTAINS "@spammy.net"
• OR Email CONTAINS "@spammer.org"
What if you have to deal with a huge list? 🤯
One solution is to invert the comparison 🔄
👉 Instead of checking if Email contains a spammy domain, extract the domain from the email and flip the logic:
Extract the email domain:
• MID( Email, FIND( "@", Email ), 255 )
Compare it against your list of spam domains:
• SpamDomainList CONTAINS EmailDomain
This approach will work better when dealing with dynamic lists too (say, lists stored in custom metadata or custom objects).
💣 CAVEATS - You have to ensure:
👉 the Email field is non-empty and properly formatted
👉 the domains match are case-sensitive
👉 avoid false positives (improbable but still a concern) by prepending and appending separators (commas) to the email domain and the spam domain list when doing the "contains" comparison