All Ideas

Idea Details

Post an Idea
This idea has been delivered and can no longer be voted or commented on. If you’d like to add to this conversation, please post a new idea.
1,590  Points voting closed
Delivered in Spring '12
Idea is generally available.

For some time there has been a discussion on CRM success about sensitive vs. insensitive salesforce IDs. The discussion goes something like follows: Normal object IDs are 15 characters and look something like the following: 01I400000009Sds. However, these IDs are case sensitive, and when utilizing tools such as the Excel Data Connector, you have the potential of running into severe trouble (VLOOKUP does not recognize case differences). Hence, Salesforce also allows you to use a case in-sensitive version of record IDs (e.g., 01I400000009Sds3e2) that runs 18 characters long (the actual formula for the conversion this is very complex). In the Service and Support world, however, we've run into the same exact problem. Email to Case Reference IDs [ ref:00D3WKx.500434K0E:ref ] are very similar to record IDs 500400000034K0E, and are also case sensitive. This causes a distinct problem when certain email clients convert these IDs to sentence-case. Can we also have the option of having case in-sensitive reference IDs?

· Flag

Latest Comment from Salesforce

  • Shannon Hale - 5 years ago

    The CASESAFEID() function introduced in Spring '12 addresses this issue. Create a formula field that wraps the id in the CASESAFEID() function. This converts the 15-character case-sensitive ID to the 18-character case-insensitive ID, for better compatibility with Excel.
  • Upvotes
  • Downvotes



from AppExchange


Help us to keep IdeaExchange clean by pointing out overlapping ideas. We'll investigate your suggestion and merge the ideas if it makes sense.



Thanks for your merge suggestion. We will review it shortly and merge the ideas if applicable.

Salesforce takes abuse situations very seriously. Examples of abuse include but are not limited to posting of offensive language or fraudulent statements. To help us process your request as quickly as possible, please fill out the form below describing the situation. For privacy and security reasons, the final outcome of an abuse case may not be revealed to the person who reported it.


Thank you for your feedback. We take abuse seriously and will investigate this issue and take appropriate action.