enable case sensitive IS, CONTAINS, ... in filter operators

[Grégoire_Miche2]

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

[SanfordWhiteman]

+1!

This would be very complex to implement if the database's underlying collation is case-insensitive, though.

Meantime, a FlowBoost script could be used to do the same in a pinch (you can narrow the list first using the UI).

var sfdcID = {{Lead.SFDC Id}},

  interestingIDs = [ 'aaa', 'BBB', 'cCc', 'Ddd' ],

  isInList = interestingIDs.indexOf(sfdcID) >= 0;

[Devraj_Grewal]

This would also be great for data management to have consistent naming.

For example:

california

California

CALIFORNIA

can all be normalized to "California". It makes for a cleaner look and easier to read.