New
enable case sensitive IS, CONTAINS, ... in filter operators
Today, the operators in filters are not case sensitive. Typically
First name is "gregoire" will return
- Grégoire
- GREGOIRE
- Gregoire
- gregoire
It would be very useful if we could have a checkbox or an option to ask for a case sensitive match.
This would be extremely useful when manipulating SFDC ID's in lookup fields, for instance. I ran into a case where I provided 250 SFDC ID's in a filter, and the smart list returned 305 leads, and yet the ID is unique ![]()
-Greg