A custom Site Visit object has an Account lookup and an Onsite Contact lookup to Contact. Coordinators fill in Account first. When they then search for the Onsite Contact, they should only be offered contacts that belong to that same account, rather than picking freely and being corrected afterwards. What should the admin configure?
Choose an answer to check it. Afterward, select any option to review its explanation.
A field dependency is the familiar way to make one choice narrow another, so it seems to fit. It filters the values of a picklist based on another field; Onsite Contact is a lookup to records, which needs a lookup filter instead.
A cross-object formula would let coordinators see which account a chosen contact belongs to, which might help them notice mistakes. It only displays data after the choice is made and doesn't limit which contacts the lookup offers.
A validation rule would keep bad data out, which covers the data-quality goal. But it only checks values when the user saves, so coordinators could still pick a wrong contact and get an error; the requirement is that wrong contacts aren't offered at all.
Lookup filters narrow the records a lookup offers, and a filter can compare a field on the target record (the contact's account) with a field on the record being edited (the visit's account). Coordinators then only see matching contacts in the search.
id q5158c8339c