A company wants to run different logic based on an Opportunity's record type. Which code segment handles this request and follows best practices?
A.
Java
List recTypes = [SELECT Id, Name FROM RecordType WHERE SobjectType = 'Opportunity' AND IsActive = True];
Map recTypeMap = new Map();
for (RecordType rt : recTypes) {
recTypeMap.put(rt.Name, rt.Id);
}
for (Opportunity o : Trigger.new) {
if(o.RecordTypeId == recTypeMap.get('New')) {
// do some logic Record Type 1
} else if (o.RecordTypeId == recTypeMap.get('Renewal')) {
// do some logic for Record Type 2
}
}
B.
Java
for (Opportunity o : Trigger.new) {
if (o.RecordType.Name == 'New') {
// do some logic Record Type 1
}
else if (o.RecordType.Name == 'Renewal') {
// do some logic for Record Type 2
}
}
C.
Java
List recTypes = [SELECT Id, Name FROM RecordType WHERE SobjectType = 'Opportunity' AND IsActive = True];
Map recTypeMap = new Map();
for (RecordType rt : recTypes) {
recTypeMap.put(rt.Name, rt.Id);
}
for (Opportunity o : Trigger.new) {
if (recTypeMap.get('New') != null && o.RecordTypeId == recTypeMap.get('New')) {
// do some logic Record Type 1
}
else if (recTypeMap.get('Renewal') != null && o.RecordTypeId == recTypeMap.get('Renewal')) {
// do some logic for Record Type 2
}
}
D.
Java
Id newRecordTypeId = Schema.SObjectType.Opportunity.getRecordTypeInfosByName().get('New').getRecordTypeId();
Id renewalRecordTypeId = Schema.SObjectType.Opportunity.getRecordTypeInfosByName().get('Renewal').getRecordTypeId();
for (Opportunity o : Trigger.new) {
if (o.RecordTypeId == newRecordTypeId) {
// do some logic Record Type 1
}
else if (o.RecordTypeId == renewalRecordTypeId) {
// do some logic for Record Type 2
}
}
Show Answer
Hide Answer
Correct Answer:
D
In Salesforce Apex development, the 'Best Practice' for retrieving Record Type IDs is to avoid SOQL queries and instead use the Schema Describe methods. Option D utilizes Schema.SObjectType.Opportunity.getRecordTypeInfosByName(), which retrieves metadata directly from the application's local cache.
There are three primary reasons why Option D is superior to the others:
Governor Limits: Salesforce imposes a strict limit of 100 SOQL queries per synchronous transaction. Options A and C consume one of these limited queries just to fetch metadata. In a complex environment where many triggers and flows execute, 'saving' SOQL for actual business data is crucial. Describe calls do not count against SOQL limits.
Performance: Fetching data from the metadata cache is significantly faster than executing a database query, leading to lower CPU usage and faster trigger execution.
Data Integrity: Option B is a common anti-pattern that will result in a runtime error. In an Apex Trigger, the Trigger.new list only contains the fields of the object itself. It does not include related fields (cross-object fields) like RecordType.Name. Accessing o.RecordType.Name directly would return null or cause a 'System.SObjectException: SObject row was retrieved via SOQL without querying the requested field.'
By using the Schema class, the developer ensures that the code is bulk-safe, performant, and does not hardcode IDs, which can vary between Sandboxes and Production environments.
