Hi all,
I'm not sure if this is an 'all Tessituras do this' or specific to our implementation. When a new account is created through our website, the new record's address is created twice and is modified by the WebAPI instantly, with the duplicate entry being inactivated. So, all new records from the website have an inactive duplicate of their mailing address.
For a while, a couple of us on the team would just update each record as they came in. Because we're kinda small, the volume isn't impractical, but this does mean we're spending time deleting something instead of doing something more productive. Does anyone know a setting or piece of code that is responsible for this that I could update in our system? This wouldn't replace real cleanup, but would be great at not needing to click into each and every new record.
Thanks!
Anthony
Opera Colorado
Hi Anthony, Looks like you are on TNEW. For us (when I was at Sydney Dance) TNEW would create an anonymous user which it would merge, but for account creation there was only one record for the constituent. I'd pop in a quick support ticket.
Yes Heath, we are on TNEW. I believe our TNEW creates an anonymous user, too. To clarify, in case I'm misreading your comment, it isn't that TNEW is creating a duplicate constituent record, but that it is creating a duplicate mailing address record. I can submit a support ticket, but I was wondering if the community here had dealt with this before. Thanks!