We've encountered an issue in v11 wherein attempting to add an affiliate to an existing household record will result in an error regarding an "inactive original source code number". While it makes sense that some records may have been created using an original source code no that is no longer active, we still may have need to add affiliates to the household record but are prevented from doing so because of a field we don't believe is used for any of our reporting/record keeping purposes.
Our solution is to simply change on the back-end the original_source_no of each record in T_CUSTOMER en masse to more generic (and less time-sensitive or esoteric) sources, but we wanted to make sure this wouldn't affect any other internal processes within Tessitura.
Any thoughts/experiences/dire warnings?
Thanks in advance, Tessiturians.
Are you on v11.0.2? We ran into this issue on that version last March, and I believe it was fixed in v11.0.3.
We are on 11.0.2 as a matter of fact. Are you saying that this issue does not come up at all in 11.0.3? Because we plan to implement the patch during our next LIVE to TEST event and I won’t bother with any coding workarounds if I don’t have to.
Thank you,
Matt Gonzales
Database Administrator
Houston Grand Opera
510 Preston St | Suite 500, 5th Floor
(v) 713-980-8702 | (f) 713-225-2574
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Chris JensenSent: Wednesday, August 29, 2012 4:30 PMTo: Matt GonzalesSubject: Re: [Tessitura Next Generation Forum] Suffering Some Stultifying Seminal Sources
From: Matt Gonzales <bounce-mattgonzales9808@tessituranetwork.com>Sent: 8/29/2012 3:10:51 PM
You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!
Yep, the issue went away for us with v11.0.3, happily, since we really wanted to preserve our original_source_no's.
Looks like the Development team would like to clean up the Original Source No on all records any way as part of general clean up of the current Tessitura LIVE data. Any reason that shouldn’t be a simple matter of just changing that field en masse on the back end? I can’t think of any internal processes that it would affect…
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Chris JensenSent: Wednesday, August 29, 2012 5:01 PMTo: Matt GonzalesSubject: RE: [Tessitura Next Generation Forum] Suffering Some Stultifying Seminal Sources
From: Matt Gonzales <bounce-mattgonzales9808@tessituranetwork.com>Sent: 8/29/2012 4:33:28 PM
I can't think of anything, either. As a field, it's purely informational, AFAIK.