We have a client who we're helping implement HEDA in a brand new instance for an advancement use case. However, they'd like the ability to scale in future phases to include current student data.
I'm used to using the standard Administrative Account approach, but the Household model makes sense for advancement. Can anyone name some obvious downsides when scaling to include things like current/prospective students? Is mixing Household and Administrative Accounts in the system of any real consequence, as long as the default account model doesn't change? Or are there any consequences to switching the default account model later on?
9 réponses
Hi @Rob Sobalvarro, you should be able to mix the Account models in the same org. If the default model is setup as Administrative, you can still have other Contacts (non-current/prospective students) attached to Household accounts. The trick is making sure the Account field is filled in upon Contact creation since the administrative account would only get created when AccountId is blank.
