Skip to main content

I’m right on the verge of “helping” my org by introducing a new record type for Contacts to solve a problem*.  They are a recruiting company and have business contacts for companies they are recruiting for, and they also have candidate contacts that they are associating with jobs they want to fill.  

 

This seems like a good use case for having two Contact record types, but I've read that record types are not recommended for Contact records most of the time, and that perhaps I should solve this with a picklist instead.  However, there are significant differences in what fields are needed for each.  Do you think my use case above is a good one for record types on the Contacts object?  Yes, I know I've given limited info... but what's your gut response or feedback?

 

*If it helps, the problem we are trying to solve is that they want to integrate with another platform for candidate data, but they will only use the standard Contact object to do that.  Our custom object for candidates cannot be used to sync.  Fortunately, they are just starting out with Salesforce, so this change would not be difficult if we do go the record-type route.

5 个回答
  1. 2023年6月9日 19:49

    Yes! You should definitely use record types for this scenario. Where did you read not to use record types on the Contact object? I am curious to know if it was for a specific reason. It does add a layer of complexity but it is worth it.

     

    Your two types of contacts are so different in nature, that you will definitely need different fields for each type. If you need to show different picklist values for the same field on both of these types of contacts, then yes your only option is record types.

     

    I have heard people recommend using Dynamic forms on the Lightning Record Page to control which fields a user sees depending on criteria on the record. I have worked in an org with this setup and it was a nightmare to figure out why a user could not see a field on the page - was it because of FLS, or the dynamic form, etc. There is no good way to see the filters controlling the show/hide of each field - you have to click into each one.

     

    I am an old school Salesforce person who grew up with record types being the only option to control which fields a user can see, so I am a little biased. I would create a page layout for each record type and then it is very easy to see/troubleshoot which fields a user can see.