I'm looking at the subscription renewal notice process, and I seem to be missing something. The docs list two sql objects associated with the report Subs Renewal Notices. I've just run a trace and that seems to agree that there are two procedures, the second being TP_GET_REN_NOTICES.
That procedure returns a row for each seat, but the result set when the report is run in Tessitura has just one row for each order. I can't figure out where this transition is handled.
I'm baffled. Can anyone point me to the missing link?
The rest of this data transformation is handled inside the application, in the window script. It’s compiled, so there’s no way to get access to it.
-Ryan
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Brian GrahamSent: Monday, January 31, 2011 12:27 PMTo: Ryan CrepsSubject: [Tessitura Technical Forum] TP_GET_REN_NOTICES - the missing link?
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Gotcha. Figured it was something like that. Thanks, Ryan.
Brian -
We've "gotten" around this by breaking the renewal invoice printing process into several reports and basically replicating the renewal invoice process through local tables and procedures. It's not what I would recommend as it means every year you have to kind of go back, remember what you've done and massage it for any changes, but if you REALLY have to do it, you can!
HeatherSeattle Rep