Opportunity Form Cleanup — Primary Contact & Duplicate Removal

Overview

The New Opportunity creation form in Salesforce had two distinct problems: redundant duplicate fields that cluttered the UI, and the absence of a required Primary Contact field. Both issues were identified during a working session with ^[1] and queued for cleanup by ^[2].

Problems Identified

Duplicate Fields

During screen review, the New Opportunity form was found to display certain fields twice — most notably Account Name, which appeared once under "Opportunity Information" and again in a second section. Entering a value in the first instance auto-populated the second, confirming the duplication was a layout artifact rather than intentional. Opportunity Name exhibited the same behavior.

These duplicates add visual noise and create confusion about which field is authoritative.

Missing Primary Contact

The standard Salesforce New Opportunity form does not include a contact lookup at creation time. Salesforce's default assumption is that contact roles are added after the opportunity is saved. For Quarra, this created a discipline gap: opportunities could be created without any named contact, making it unclear who the rep was actually working with at the account.

"I want to enforce the discipline that when you have an opportunity, there's a specific person you're talking to. Makes sense. And you're putting that in there."
— Lincoln Durham, Quarra

Solution

Remove Duplicate Fields

Strip redundant field instances from the New Opportunity layout. Only one instance of Account Name and Opportunity Name should appear on the creation form.

Add Required Primary Contact Lookup

Add a Primary Contact lookup field to the New Opportunity screen. This is a lookup to the Contact object, filtered to contacts associated with the selected Account. Making it required at creation time enforces the expectation that every opportunity has a named point of contact from the start.

This is technically a lookup field (not a simple text field), which requires slightly more configuration than a standard field — but is fully supported in Salesforce and consistent with how Account Name already works on the form.

Design Considerations

Timing of requirement: Lincoln acknowledged that if Quarra moves away from the Lead object and creates more early-stage opportunities, there may eventually be cases where a contact isn't known at creation time. The current decision is to enforce the requirement now while the team is building Salesforce habits, with the option to relax it later.
Contact roles vs. primary contact: Salesforce supports multiple contact roles on an opportunity (e.g., decision maker, advisor, GC). The Primary Contact field is a separate, simpler lookup intended to capture the single person driving the engagement — not a replacement for the full contact roles panel.

Implementation Notes

Asymmetric (Mark Hope) owns the layout cleanup and field addition.
Lincoln (Quarra) will send Mark a full opportunity field audit covering Close Won required fields and other duplicates, to be addressed in the same pass.
Related: the "Industry Segment" dropdown also needs Interior Design and Landscape Architect added to both the Account and Opportunity objects. See ^[3].

^[4]
^[5]
^[6]
^[7]