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
There's a setting for TNEW -- in T_DEFAULTS, I think -- that saves a copy of the address if the user makes a change on TNEW. So this is standard behavior if you have that option turned on. We have it turned on because otherwise if a patron updates their address on TNEW it will overwrite the existing address and you lose the old address. For us, we would rather have the duplicates come in at account creation and be assured that we have a history of addresses on the account. It comes up sometimes about where something was sent / when or why an address was changed. We find the extra level of detail useful.
Anne M Robichaux said:here's a setting for TNEW -- in T_DEFAULTS, I think -- that saves a copy of the address if the user makes a change on TNEW.
I believe it is SaveAddressCopyOnChange in LTR_TNEW_SITE_CONTROLS. Our choice is overwriting an old address with a new one, or creating duplicates. No perfect option, but we create and deal with the duplicates, since no later than when we asked support about this back in 2014.
That's it!