Hi,
We don’t plan on using the Accounts table/entity. Is there a way to force the User to always pick a Contact instead of potentially selected an Account?
Thanks!
Your question is missing some details and context, so I am going to assume you are talking about the Customer field. If this is incorrect, please let me know. I have found that most records that have a Customer (polymorphic) field also have a dedicated Contact and a dedicated Account field. You can hide the Customer field and the Account field from forms and views and only use the Contact field instead.
Clarifying definition: A polymorphic field is a lookup field where a user can select a single record but can choose that record from two or more tables (like Account or Contact). Regular lookup fields only allow you to select a record from a preset (single) table.