Skip to main content

We're making the shift from the administrative account model to a hybrid account model to better suite our corporate relations needs.

 

We've noticed when we link a contact to a business/organization account via the standard account name field, the Primary Contact on the account gets set to that contact.  Ideally we'd leave the Primary Contact to be populated by a user. 

 

I am guessing this has to deal with the ACCT_IndividualAccounts_TDTM trigger.  Can anyone confirm this?  Also, any ideas for how to set the filter field/filter value to only run for the administrative accounts?

 

@Sector: Higher Education @HED Corporate & Foundation Relations

8 risposte
  1. 12 gen 2022, 22:27

    I don't know for sure, but I think you're probably correct @Nick Lindberg that the EDA trigger is populating the primary contact field on Accounts for all record types. As loathe as I am to go against standard functionality, I'd argue that when you enter hybrid account territory, you consider turning off the standard EDA trigger that is driving this.

     

    If I remember correctly, the Primary Contact field on the Account is a carryover from NPSP that was added when Household Accounts were brought into EDA. If you aren't using Household Accounts, that field doesn't have much functional use, apart from from automating Account ownership around the Primary Contact ownership. Again, this isn't something you'd typically want with traditional Business Organization accounts.

     

    In short, if you're not using the Primary Contact field for any functional purpose (compared to, say, how fundraisers use Household Accounts), deactivating the ACCT_IndividualAccounts_TDTM trigger may have no real impact on your used functionality. As long as you're ok with how account ownership is assigned in the absence of this trigger, you're probably good to go.

     

    As always, test carefully in a sandbox, and consider the long-term impacts of bypassing standard functionality for a current need. But it seems to me that if you have no real use for the Primary Contact field on the Account, disabling that functionality will give you a simpler path to implementing your hybrid account model.