Question

Difficulty: MediumFlow Types and Triggers

A business requirement specifies that whenever an Opportunity record is created or its stage is modified, the custom field Target_Fulfillment_Date__c on that same Opportunity record must be calculated and populated immediately. The solution must provide optimal system performance by avoiding additional DML operations and unnecessary recursive save cycles.

Which automation design should be implemented to meet this requirement?

  1. A
    A Record-Triggered Flow configured for Actions and Related Records with an Update Records element targeting the triggering Opportunity record
  2. A Record-Triggered Flow configured for Fast Field Updates on record creation and updateAnswer
  3. C
    A Record-Triggered Flow configured with an Asynchronous Path to calculate and commit the date field in a separate transaction
  4. D
    A Schedule-Triggered Flow executing at scheduled intervals to query and process recently modified Opportunity records in batches

Answer

A Record-Triggered Flow configured for Fast Field Updates on record creation and update
A Record-Triggered Flow configured for Fast Field Updates (before-save) executes before the record is saved to the database. It updates fields directly on the triggering record via assignment without needing an Update Records data element, preventing additional DML operations, recursion, and governor limit overhead.

Step-by-Step Solution

1
Identify the target record and automation timing
The requirement targets the same triggering record (Opportunity) and requires immediate field population upon save.
Determining whether updates affect the triggering record or related records determines the trigger configuration.
2
Evaluate the optimal Flow trigger type for same-record updates
Fast Field Updates (before-save record-triggered flow) update fields directly on the triggering record before it is committed to the database.
Before-save updates avoid extra DML statements, avoid re-triggering execution rules, and execute significantly faster than after-save updates.
3
Select the configuration meeting performance and zero-recursion criteria
A Record-Triggered Flow set to Fast Field Updates satisfies all constraints.
Actions and Related Records or asynchronous options add unnecessary transactional overhead or delay the update.

Key Concept

Fast Field Updates (Before-Save) in Record-Triggered Flows
Estimated Time:1m 0s
Rate this question