![]() What if there are Accounts with dozens, even hundreds, of Contacts? To separate out Bruce-the-alumni from Alfred-the-recruiter, you may want to add Contact Roles to the Account.This will work best if Accounts and Contacts are, at least, Public Read-Only. How about Security? If Accounts are Private in the OWD (Organization Wide Defaults) or if Contact is ‘Controlled by Parent’, you’re going to have to think through record visibility.However, the organization has to accept, as a policy decision, that sometimes they’re working with ‘mostly current’ data. What if my information is old or incomplete? In my opinion, some data is better than no data, and it will be updated when you next hear from the Contact. ![]() What if my contact isn’t working anywhere? Full-time students will not have a main job, so you need to consider a bucket Account for the students currently enrolled, then move them when they graduate.There are a number of reasons why this could get complex, therefore it’s up to each Org to review the best practice. The mechanism is straight-forward, but it's important to coach/train your users on how to create/manage the Affiliations (not to directly update the Account on the Contact). (i.e., only the new Affiliation record is Primary = true). Add a Flow to set the “Primary” checkbox on the other (existing) Affiliation records to false.Add a Process Builder on the Affiliation object: When a record is marked as "Primary," update the Contact with the Account of that record.The business rule here is that each Contact can only have one Primary Affiliation. Ensure that your Affiliation object has a “Primary” checkbox: This field allows a user or contact to identify their main relationship.There are three steps to putting this Affiliation-driven contact in place: On the flip side, if you need to review the ABC Bank record, you’ll find Chris and all the other currently associated affiliations as Contacts. If you, as a Salesforce user, need to look at the Contact record, you probably want to understand how the Contact identifies themselves – now when we look at Chris’s record, straight away we see Chris James, ABC Bank. However, Jo is probably going to identify one relationship as primary – so let’s use this one relationship to set the Account on the Contact record. Now it’s possible that someone can have multiple active affiliations – Jo is working here, on the board there and consulting too. Let’s assume for a minute that in your affiliation record, you have a start and end date for each affiliation – no end date means that there’s an ongoing relationship, e.g., Jill is working at the bank or Pat is studying at the university. Which community organizations they volunteer with.This object allows you to create multiple relationships between Accounts and Contacts. HEDA (Higher Education Data Architecture) is included as an “Affiliation junction” object – this may exist in your org as an ‘Employment History’ object or similar. We believe so: An Affiliation-driven Contact. Bucket Accounts: A simple solution, but limited to no more than 10,000 contacts per account (Salesforce best practice).Household Accounts: This can be a complicated concept for users – where does one household start and the next one end? We have to know the relationships between individuals and know how and when to maintain them.Administrative Accounts: Creates two records for every one, and the Account record becomes meaningless clutter which the analysts and data miners have to work around.Person Accounts: Difficult to support a blended O2I and B2B model in the same org, it is not compatible with all AppExchange products and is known to have other issues.Bucket Accounts: Lump all the Contacts into a single account.Household Accounts: Create an Account for the Contact, their spouse, parents, siblings, as required.Administrative Accounts: Create an Account for every Contact record.Person Accounts: A ‘standard’ Salesforce function which rewrites the data model, turning the Account record into a ‘Contact’.What are the traditional Salesforce configuration options for a Higher Education Institution? Salesforce, however, mandates that all Contacts are associated to an Account. But we don’t want the Account to dictate how we deal with the Contact. Sure, Accounts are important – we want to know about the schools we recruit students from, the companies where they end up working, the foundations who contribute to alumni relations and the partner organizations we work with. Working in the Higher Ed space, or any B2C O2I* organization, can present the Salesforce Administrator with a headache: how to manage the Account of the Contact record, when the Contact is as important, if not more important, than Account.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |