An Apex trigger creates a Contract record every time an Opportunity record is marked as Closed end Won. This trigger is working great, except (due to a recent acquisition) historical Opportunity records need to be loaded into the Salesforce instance.
When a test batch of records are loaded, the Apex trigger creates Contract records. A developer is tasked with preventing Contract records from being created when mass loading the Opportunities, but the daily users still need to have the Contract records created.
What is the most extendable way to update the Apex trigger to accomplish this?

Question

An Apex trigger creates a Contract record every time an Opportunity record is marked as Closed end Won. This trigger is working great, except (due to a recent acquisition) historical Opportunity records need to be loaded into the Salesforce instance.

When a test batch of records are loaded, the Apex trigger creates Contract records. A developer is tasked with preventing Contract records from being created when mass loading the Opportunities, but the daily users still need to have the Contract records created.

What is the most extendable way to update the Apex trigger to accomplish this?

Danilo Nogueira · Accepted Answer

Use a Hierarchy Custom Setting to skip executing the logic inside the trigger for the user who loads the data.

Danilo Nogueira · Answer

Use a List Custom Setting to disable the trigger for the user who loads the data.

Danilo Nogueira · Answer

Add a Validation Rule to the Contract to prevent Contract creation by the user who loads the data.

Danilo Nogueira · Answer

Add the Profile ID of the user who loads the data to the trigger so the trigger will not fire for this user.

Question list

List of questions

Question 1

(0)

Question 2

(0)

Question 3

(0)

Question 4

(0)

Question 5

(0)

Question 6

(0)

Question 7

(0)

Question 8

(0)

Question 9

(0)

Question 10

(0)

Related questions

Question 288 - Certified Platform Developer II discussion

Suggested answer: C

0 comments