I've been recently asked to alter a canned report for Development. They want the Print Acknowledgement Letters report to include an extra field that will specify which text their Word template will generate when they print their letters each day; a simple concept, yes.
However, I am not an Infomaker expert - or fan, for that matter - and am generally leery of mucking around with Tessitura's canned reports if it's not necessary. So, my standard answer is to make use of the highly preferable Visual Studio and put most reports on our Reporting Services site.
My concern with this strategy is by not using the canned report, am I missing out on some sort of internal process (i.e. a stored procedure) that needs to run in the background to make certain important updates, to whatever myriad tables in Tessitura may be involved, in the running of the original report that won't be done using Reporting Services?
Also, are we maybe overthinking this? Is there perhaps a better way to accomplish this task - perhaps even one that Tessitura already designed but is not being implemented at the moment - wherein for whatever different kind of contribution we receive, we can have different verbiage automatically chosen for the printing of the letters? Or is a well-designed Word merge letter template the best way?
Or do I need to start taking some Infomaker and Tessitura Reporting classes pronto?
Thank you in advance, Tessiturians.
Matt Gonzales
As Lucie described, it is possible to both run the standard report and your own code, i.e. create a custom sproc, run AP_ACKNOWLEDGEMENT_LETTERS within it, sending the output to a temporary table, and then sending whatever you want of that data + additional data to a custom InfoMaker report.
We have a number of custom acks, both for Devo and for ticketing orders, that work this way, and are very happy with the results. The same basic idea works very well for custom renewal notices, too, running TP_GET_REN_NOTICES within a custom spoc in that case.