Hope this is possible, but I fear it is not.
I would like for the standard Acknowledgment report to have "Program Book Name" as an optional parameter and then have the corresponding name returned in the data set along with the next payment due date and amount. Since I'm certainly not going to start hacking away at AP_ACKNOWLEDGEMENT_LETTERS, I thought about copying it to LP_ACK_LETTERS and making the changes there and then tying a custom report to it that would do all of the nifty acknowledgement tricks (i.e. look in t_format_info to get the correct infomaker object).
Is this advisable? Possible?
We use a local ack letter procedure so that we can add a couple of fields that aren’t in the original, the program name being one of them. In InfoMaker I copied d_ack_letter_report to create ud_ack_letter_report, added my extra fields, attached it to my acknowledgements in t_format_info, and that’s that.
Lucie
___________________________________
Lucie Spieler
IT Development and Training Manager
Editor, Season Program
Florida Grand Opera
8390 NW 25th Street
Miami, FL 33122
305.854.1643 x 1521
Box Office: 800.741.1010
To Give a Gift: 305.403.3315
www.FGO.org
2010-2011 | 70TH SEASON | THE MYSTERIES OF LOVE
Turandot | The Tales of Hoffmann | Don Giovanni | Cyrano
Lucie,
Do you have multiple Program Names per constituent? If so, how do you choose the correct one for the letter you are trying to run?
Unknown said: Do you have multiple Program Names per constituent? If so, how do you choose the correct one for the letter you are trying to run?
We have a both a custom ack letter report, and multiple program names. We include as many as are desired (three I think) in the ack letter output, which is later mail-merged, and I believe that depending on which letter is being merged at the time, only the desired pname is included in the final letter output.
Chris,
Thanks for the info. We are trying to reach the Holy Grail of not having to merge the Ack Letters. So I need to specify the requested program name as a parameter. We've worked around this by just creating a separate report for this particular letter. The new report calls its own local SP and bypasses the standard report altogether.
Not the most elegant solution, but it works and is saving the devo folks quite a bit of time.
Unknown said: We are trying to reach the Holy Grail of not having to merge the Ack Letters.
We are trying to reach the Holy Grail of not having to merge the Ack Letters.
We tried to go there, too, after we moved to Tessitura, but in the end, the ability to reach in and individually tweak the letter output when desired kept a total, non-merge, Ack letter report out of reach. If you can arrive at such a report that meets all needs, I salute you! :-)
Hello all,
I have a very newbie question!
Can I ask how you are managing the d_ack_letter_report files? Are you using Infomaker, the grsetup application, or a differnent utility?
If you are using InfoMaker, do you have it connect directly to the Tessitura DB in the manner that grsetup does?
Many thanks.
Nicholas
InfoMaker here. One D object, one custom sproc with the standard output fields plus (IIRC) about 30 additional fields. Then 40+ different "letters" to choose from when running the standard Ack report, based on our various custom mail-merge docs.
Thanks Chris,
And do you use the Tessitura DB credentials in Infomaker to connect to the Tessitura database and associated files?
Cheers,
Unknown said: And do you use the Tessitura DB credentials in Infomaker to connect to the Tessitura database and associated files?
I'm not 100% sure what you mean: there are no special credentials in our custom sproc, i.e. exec on it has been granted to impusers and it runs like most any other Tessitura report sproc.
I'm going to tack on a reply to Levi's original question. I've seen program name information added to the acknowledgement reports by simply adding a subreport to your acknowledgment letter to display just the program type and preferred name for that customer_no. Then you don't have to mess with creating a local version of AP_ACKNOWLEDGEMENT_LETTERS.
Due to the issue with some posts coming through email but not making through to the thread, I'm pasting Levi's reply to Brian here for reference:
"Thanks Brian! That is definitely a more elegant solution. But that sort of falls out if the users are running the report with the intent of doing a word merge doesn’t it? The sub-report data wouldn’t be included in the data set sent to the merge document. Or do I have that twisted up in my head?
Levi Sauerbrei"
Levi, you're right that a subreport would break the ability to word-merge that additional data, but I thought you were trying to avoid merging altogether.