Our new data entry person created some new household Accounts from the New Account menu item on the Accounts tab rather than by choosing New Contact from the Contacts tab and leaving the Account field blank. When this happens, a mess ensues.
I know this is a training issue, but I've had this happen to me several times over the years. Training doesn't always do the trick. Seems that the idea of an "account" is more intuitive to some folks than the idea of a "contact".
So I'm wondering...does anybody use a software solution to prevent creation of a HH Account from the Accounts tab, but still allow NPSP's triggers to create the HH Account upon creation of a new Contact?
I tried a simple validation rule based on rectype but that blocked NPSP from creating the Account.
Is there a validation formula that can allow a NPSP trigger to create the Account but prevent a user from doing it in the UI?
Or another method?
Or is the best practice just training?
If the validation rule idea doesn't work out, here's another idea that may not (completely) meet the need, but might be worth some exploration: If you opt your users - in their personal settings - to automatically use the default record type for Accounts, and if "Organization" is the default record type, then when they create an Account from the Account tab, it would skip the record type selection and create an Organization Account. Might that be enough to get their attention/prevent the problem? (You may or may not want to display the record type on the page so it can be changed.) (Profile/Avatar/Photo in top right corner->Settings->Display & Layout->Set Default Record Types
