A Salesforce administrator at a commercial real estate agency needs to automate a field update process on a custom object named Property Listing. When a Property Listing record's Status field is changed to 'Under Contract', two fields on that same Property Listing record must be automatically updated: the Pending Date field must be set to the current date, and the Escrow Status field must be updated to 'Pending Deposit'. The solution must be declarative, optimized for maximum performance, and avoid unnecessary database writes or re-triggering the Salesforce order of execution. Which automation tool configuration should the administrator select to meet these requirements?
- A Record-Triggered Flow configured for Fast Field Updates (before-save trigger)Answer
- BA Record-Triggered Flow configured for Actions and Related Records (after-save trigger) with an Update Records element
- CA Roll-Up Summary field configured on the Property Listing object to evaluate and set the pending status
- DAn Autolaunched Flow called iteratively inside a loop from Process Builder to update the record fields
Answer
A Record-Triggered Flow configured for Fast Field Updates (before-save trigger) is the optimal choice for updating fields on the record that initiated the automation.
The correct choice is the Record-Triggered Flow configured for Fast Field Updates (before-save trigger). When automation only needs to modify fields on the record that initiated the event, Salesforce best practice dictates using a before-save record-triggered flow. Because the updates happen in memory before the record is written to the database, no additional DML statement is required, minimizing system overhead and preventing re-triggering of the order of execution.
Step-by-Step Solution
Key Concept
Declarative Automation Selection: Before-Save vs. After-Save Record-Triggered Flows