Sales reps miss key fields when filling out on opportunity record through the process. Reps need to move forward Win unable to enter previous stage…

This scenario requires a solution that both guides users and enforces data entry at specific points in the sales process.

1. Configure Opportunity Path (C): This provides a visual representation of the sales stages, guiding reps through the process.

2. Enable guided selling (A): As part of the Path configuration, an administrator can specify "Key Fields" and "Guidance for Success" for each stage. This prompts users to fill in critical information as they progress.

3. Use Validation Rules (B): To strictly enforce the requirement, a validation rule can prevent a user from moving to the next stage if a key field is blank. For example, a rule can fire when the StageName field is changed, checking if a corresponding field is filled out.

This combination provides both user-friendly guidance and necessary data integrity enforcement.

D. Use Flow to mark fields required:

A Flow would create a custom user interface, which is more complex than necessary. Path and Validation Rules are the standard, declarative tools for this specific requirement.

E. Mark fields required on the page layout:

This makes a field universally required on record creation and edits, regardless of the opportunity's stage. This is too restrictive and does not meet the stage-specific requirement.

---

1. Salesforce Help Documentation, "Guide Users with Path": This document details how to set up a Path. It states, "At each step of a path, you can highlight key fields and include guidance for success... A path guides your users along the steps in a process, such as working an opportunity from a new lead to a successfully closed deal." This supports the use of both Path (C) and its guided selling capabilities (A).

2. Salesforce Help Documentation, "Validation Rule Examples": This resource provides examples of validation rules. The principle shown in the "Opportunity Validation Rules" section can be applied here, such as creating a rule with the formula AND(ISCHANGED(StageName), ISBLANK(NextStep)) to require the NextStep field be populated before the stage can be changed. This supports the use of Validation Rules (B) for enforcement.

3. Salesforce Help Documentation, "Considerations for Page Layouts and Field-Level Security": This document explains that making a field required on a page layout means "users must enter a value for the field when they create or edit a record." This confirms that this option (E) is not stage-specific and is therefore incorrect for this scenario.