Hello Community!
We are evaluating if we should use a single record type for contacts for the entire life cycle of the student from recruitment, success, alumni and donations/advancement or use many.
We started with the high school and university recruitment process 5 years ago, however we have grown in Salesforce and now we have more processes such as advancement, student success, 360, continuing education, etc. Also this year we will include recruitment and admissions of postgraduates, masters, etc.
Our analysis starts to complicate when we think about an active high school student can be a college candidate and the same is true of a graduate college student. It can also happen that a former student requires a master's degree or that an employee is a former student and in turn a candidate for a master's degree. There are many combinations and many departments inside our institution that can share student information at the same time.
One idea is to use a single record type on contact, but on other objects such as opportunities, applications and others utilizing more record types. We are also using a custom field called “Role” that is a multipicklist where a contact can have N profiles such as career candidate, active student, employee, high school alumni, etc.
What do you think? Any best practice or something to take into account in the decision?
Thank you so much
@Sector: K-12 Education is this on the roadmap for the #K-12 Architecture Kit and if we are going to deprecate the record types how will it affect the @SFDO Student Success Hub K-12 Customers
