<< Prev Question Next Question >>
Question 54/59
Given the following trigger implementation:
trigger leadTrigger on Lead (before update){
final ID BUSINESS_RECORDTYPEID = '012500000009Qad';
for(Lead thisLead : Trigger.new){
if(thisLead.Company != null && thisLead.RecordTypeId != BUSINESS_RECORDTYPEID){ thisLead.RecordTypeId = BUSINESS_RECORDTYPEID;
}
}
}
The developer receives deployment errors every time a deployment is attempted from Sandbox to Production.
What should the developer do to ensure a successful deployment?
trigger leadTrigger on Lead (before update){
final ID BUSINESS_RECORDTYPEID = '012500000009Qad';
for(Lead thisLead : Trigger.new){
if(thisLead.Company != null && thisLead.RecordTypeId != BUSINESS_RECORDTYPEID){ thisLead.RecordTypeId = BUSINESS_RECORDTYPEID;
}
}
}
The developer receives deployment errors every time a deployment is attempted from Sandbox to Production.
What should the developer do to ensure a successful deployment?
Recent Comments (The most recent comments are at the top.)
C
Because the only way to have the same Record Type with the same ID both in a Prod or in a Sandbox is possible if the Record Type is existing in the Prod and the Sandbox have been generated from that Prod.
In this Case the Profile, Role, Record Types have the same ID in the Sandbox.
If the Record Type have been created into the Sandbox for Dev purpose, then moved to the Prod, the ID will never be the same.
and it is a again the Best Practice to hard code any ID.
We have to work with the API Name of the Record Type and to get its ID by Coding, so the code will not be impacted when moving from a Sandbox to another Org.
Right Ans is A, you cannot upload something with an id of other org into the production ORG because in this ORG the ID is different.
the right answer is A, as another exam of the same site implies: https://www.freecram.com/question/Salesforce.PDI.v2021-06-20.q54/given-the-following-trigger-implementation-trigger-leadtrigger-on-lead-before-update-final-id-business