A company manages partner onboarding using a custom object named Partner Application, which shares a Lookup relationship with the standard Account object. An administrator is tasked with building automation for two distinct business needs:
1. Update custom fields on the triggering Partner Application record prior to database commit to ensure optimal performance without triggering additional workflow cycles.
2. Recalculate and update a custom number field on the parent Account record to track the total count of approved Partner Applications.
Which TWO declarative solutions should the administrator implement to fulfill these requirements?
- A Record-Triggered Flow optimized for Fast Field Updates (before-save) on the Partner Application object.Answer
- A Record-Triggered Flow configured for Actions and Related Records (after-save) to update the parent Account record.Answer
- CA Roll-Up Summary field on the Account object that calculates the total count of related Partner Application records.
- DA Record-Triggered Flow configured for Actions and Related Records (after-save) to update fields on the triggering Partner Application record.
Answer
The administrator should implement a Record-Triggered Flow optimized for Fast Field Updates (before-save) for same-record field modifications, and an after-save Record-Triggered Flow (Actions and Related Records) to update the parent Account record.
Fast Field Updates (before-save flows) are specifically designed for modifying fields on the triggering record before it is committed to the database, avoiding extra DML operations. Meanwhile, updating parent/related records on a Lookup relationship requires an after-save Record-Triggered Flow because standard Roll-Up Summary fields are restricted to Master-Detail relationships.
Step-by-Step Solution
Key Concept
Selecting optimal automation tools based on trigger timing (before-save vs. after-save) and relationship type limitations (Master-Detail vs. Lookup).
Estimated Time:1m 30s