CRT-403 practice question 19 of 35

Universal Containers needs the 18-digit record ID from Opportunity records when exporting data to Excel in order to ensure each record is treated uniquely. What formula should an app builder use to create this new field?

Full set: 291 questions
Answer options
A: ISNUMBER(Id)
B: CASESAFEID(Id) Correct answer
C: TEXT(Id)
D: VALUE(Id)
Correct Answer:
B. CASESAFEID(Id)
Explanation

The standard Salesforce record ID is a 15-character, case-sensitive string. When exporting data to applications like Microsoft Excel, which can be case-insensitive, these 15-character IDs can be treated as duplicates, leading to data integrity issues. To prevent this, Salesforce provides an 18-character, case-insensitive version of the ID. The CASESAFEID(Id) formula function is the designated method to convert the standard 15-character ID into its 18-character, case-safe equivalent directly within a formula field. This ensures each record is uniquely identified in external systems.

Why Incorrect

A. ISNUMBER(Id) returns a boolean value (TRUE/FALSE); it does not convert the ID format.
C. TEXT(Id) converts a value to a text string. It would return the original 15-character ID, not the required 18-character version.
D. VALUE(Id) attempts to convert a text string to a number and would cause an error because record IDs contain non-numeric characters.

References

1. Salesforce Help Documentation, "Formula Operators and Functions I–V": Under the CASESAFEID function description, it states: "Converts a 15-character ID to an 18-character case-insensitive ID. ... Use CASESAFEID for any ID fields, including those for custom objects." This directly supports the use of this function for the stated purpose.

2. Salesforce Developer Documentation, "Formula Functions and Operators": The entry for CASESAFEID(objectId) specifies its purpose is to "Convert a 15-character ID into the 18-character, case-insensitive representation of the ID." This confirms it is the correct function for creating a case-insensitive identifier.

3. Salesforce Knowledge Article 000323213, "Convert a 15-character Id to an 18-character Id": This article explains, "Some applications... do not recognize the difference in case of the 15-character Id and can result in data corruption. To prevent this, Salesforce has the 18-character Id which is case-safe." It recommends using the CASESAFEID() formula as a primary solution.

Scroll to Top