Hi folks,
X-posting this from Ticketing where it didn't get any responses:
* * *
We just printed our subscription renewal notices, and did so based on a list so these could be restricted only to those constituents who did not renew on their own.
We also used this list to run an output set to merge to mailing envelopes. The output set (and envelopes) are ordered by constituent ID, but the Subscription Renewal Notice utility ran with nine (out of 160) invoices out of order at the end. (All of the preceding invoices were in order by constituent ID).
Does anyone know what caused that result? Is this ordering caused by InfoMaker or the Impresario stored proc?
Are you using a custom subscription form and procedure? I'd double check the stored procedure first. There might be a weird Sort By criteria tacked in there that you aren't expecting. That tripped me up last year anyway.
On a related note, when I run our subscription forms I also save the report data to excel after it generates. It outputs the data in the same order that the forms are printed. I then have our envelopes printed using that data, in that order. Then it doesn't matter if forms are out of order for some reason. Haven't had any problems since we started doing it that way!
Are you using a custom subscription form and procedure? I'd double check the stored procedure first. There might be a weird Sort By criteria tacked in there that you aren't expecting. That tripped me up last year anyway.On a related note, when I run our subscription forms I also save the report data to excel after it generates. It outputs the data in the same order that the forms are printed. I then have our envelopes printed using that data, in that order. Then it doesn't matter if forms are out of order for some reason. Haven't had any problems since we started doing it that way!From: Nick Reilingh <bounce-nicholasreilingh4883@tessituranetwork.com>Sent: 5/27/2014 11:43:11 AMHi folks,X-posting this from Ticketing where it didn't get any responses:* * *We just printed our subscription renewal notices, and did so based on a list so these could be restricted only to those constituents who did not renew on their own.We also used this list to run an output set to merge to mailing envelopes. The output set (and envelopes) are ordered by constituent ID, but the Subscription Renewal Notice utility ran with nine (out of 160) invoices out of order at the end. (All of the preceding invoices were in order by constituent ID).Does anyone know what caused that result? Is this ordering caused by InfoMaker or the Impresario stored proc?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!
From: Nick Reilingh <bounce-nicholasreilingh4883@tessituranetwork.com>Sent: 5/27/2014 11:43:11 AM
If you're using the 'out of the box' renewal form provided by Tess then you would be using their procedure. You are correct that you shouldn't modify that one. But if you have a custom renewal form (as we do) it's definitely possible that you have a custom procedure behind it which you can modify to your heart's content!