Definition
In Salesforce, the unique 15-character (case-sensitive) or 18-character (case-insensitive) alphanumeric identifier automatically assigned to every record, used as the primary key for referencing records across the platform.
Real-World Example
Consider a scenario where the system admin at BrightEdge Solutions is working with ID to control how users interact with Salesforce data and features. After configuring ID in the sandbox and validating it with key stakeholders, they roll it out to production. User adoption improves because the interface now matches how teams actually work.
Why ID Matters
In Salesforce, an ID is a unique alphanumeric identifier automatically assigned to every record. IDs come in two formats: 15-character (case-sensitive) and 18-character (case-insensitive). The 18-character version adds a 3-character checksum suffix that makes IDs case-insensitive, useful for systems that don't preserve case. Both formats refer to the same record; you can convert between them programmatically. IDs are the primary keys used for referencing records across the platform, in URLs, in SOQL queries, in Apex code, and in integrations.
The first three characters of an ID are the key prefix, which identifies the object type (like 001 for Account, 003 for Contact, 006 for Opportunity, plus prefixes for every custom object). This means you can sometimes infer the object type from the ID alone. IDs are immutable and globally unique within an org; once assigned, they don't change. For integrations, IDs are how you reference Salesforce records from external systems. Mature integrations use 18-character IDs to avoid case sensitivity bugs in external systems.
How Organizations Use ID
- •TerraForm Tech — Uses 18-character IDs in all integrations to avoid case-sensitivity bugs in their external data warehouse.
- •CodeBridge — Trains developers on key prefix conventions so they can identify object types from IDs during debugging.
- •Quantum Labs — Treats Salesforce IDs as the canonical reference in all integration design, since they're globally unique and immutable within an org.
