I have a use case where we want to take the primary contact for an account. For example, the primary person we work with at a business or school.
There is an EDA field - Primary Contact already created and is important to the ACCT_IndividualAccounts_TDTM trigger. I'm curious if I could use this field for my use case or if I should create a separate field for the use case.
I'm thinking similar to how the Primary Contact is used for NPSP - default account model or business/organization:
https://powerofus.force.com/s/article/NPSP-Primary-Contact-v-Affiliation#ariaid-title2.It appears that this already works for other Account types, which is probably about to cause me an enormous headache.
Apparently someone didn't read the comment in the field description and used the hed__Primary_Contact__c field as a merge field in a document where the "primary contact" of a business organization was mapped to the merge field. Which looks like it was probably done back in 2020 or early 2021. But since it pulled in a contact record (and usually the correct one) nobody noticed it until now.
And that flawed assumption that the "Primary contact" was what was needed for this use case is about to make my life way more interesting.
