Malik_Zafar2

Thank you guys.The problem with segmentations is that records can only qualify for one at a time. We often have records that will qualify for more than one segment, so we're finding smart lists to be more useful.

Ahh, it worked. I had populated the field incorrectly.This is fixed now, but originally I had forgotten to add the quotes to the end of the New Value.Thanks Sanford! This is amazing

So this is what I hope to happenMatchable Email CONTAINS .mil""And it would ideally show results like these:bob.smith@us.army.milbugs.bunny@us.navy.milmike.jones@us.airforce.mil(all examples)however when I use the above logic "Matchable Email CONTAINS .mil""" I don't get any results back. If I simpl...

Sanford, what if I want to look at just the very end of an email addressfor example, for some govt domains you have@us.army.mil@us.navy.mil@us.airforce.milIn this example, I only want to filter for domains that end in ".mil". I used the steps above, but that doesn't seem to work in this case. Or am ...

so if I am just starting out and creating the Matchable Email field, I would first need to run a batch to transfer all {{lead.Email Address}} of all records to that new field, correct? With very large databases, is it recommended to do this in waves instead of one massive batch?

why will it never happen, Sanford?

This sounds like a bug, but has anyone been able to pinpoint a cause or solution to this?I just noticed we have leads who've been scoring for 6 months and in Salesforce1) The "Lead Score" value is updated and shows the correct number2) The "Score" tab in Salesforce is blank3) The "Interesting Moment...