I’m doing some database cleanup and have a number of accounts that were tagged with an incorrect constituent type when they were converted during the Tessitura integration. For example, id 12345 “Mr & Mrs Smith” is tagged as a corporate constituent type, but should really be a household. However, I have no idea what first name or even first initials are, so I can’t change the type in the front end of the client. (I should mention that all of the accounts I've checked are ancient and have no recent activity on them).
What is the harm/is there harm in me changing the type in SQL so that I have a more accurate count of constituent types? Or would you choose a placeholder letter/name? Or is this one of those things I should just live with?
Kathleen Smith said:What is the harm/is there harm in me changing the type in SQL so that I have a more accurate count of constituent types?
You'd run into no issues with changing a customer type via SQL, though making hhold records with no affiliates may end up with records that confuse Tess.
Kathleen Smith said:Or would you choose a placeholder letter/name?
This refers to a fname perhaps? If you're creating hhold affils for the new hholds above, and you have no fnames, yes, I would probably substitute "Mr." and "Mrs." for the fnames, lacking anything else. I think SQL would let you create constituents without a fname, but Tess will complain if you open one of these in the client.