Skip to main content

The Case Page Layout requires that we associate the case with a contact and does not require the association with an account.

 

Because our org has enabled person accounts, we would prefer one field called "Person Account" when creating a case.

 

The reason we want this is because the team is confused as to why there are two fields that they need to be input when they create a case.

 

My solution right now is to create a custom field call Person Account and have a filter set so that they can only Select from person accounts. Then have a trigger that will auto-populate the standard account and contact fields on the record. I prefer this solution so that as the team scales there is "one" field for the team to fill in as well as a method for making sure that the team is always creating person accounts and not "Account" records or "Contact" records.

1 comentario
  1. 22 feb 2021, 0:37
    @Matthew Metros We ran into that same thing. We noticed that if you create the case from the Account's related list of cases, you can just show the contact field and the account fills in automatically. We have other processes that if the case is created elsewhere that we programmatically update the account from the contact chosen.