Ways to Add "Ticket" Info to Receipt Ticket Designs?

Hi, 

We finally got our receipts working correctly on our BOCA printers. So now I am going back in to update our Receipt Design since we never touched it after Tessitura built it for us (our receipt printer never worked so there was never a point to look at the design until today). 

Anyway, I think I have all the basics that we need:
Data - Card #
Data - Cardholder
Data - Amount
Data - Authorization Code 
Plain Text - Organization Name
Plain Text - No Exchanges/Refunds (don't know why we have this since we do offer refunds, but I'll leave it for now)

The only thing I am missing is that What. Meaning, what performance or membership or whatever did the credit card just pay for. I looked in the Help System and it seems that the type of info I want can only go onto a ticket and not on a receipt. The problem is if I were the patron, I would look at that receipt and have no idea what that $15 went for (was it for an Adult ticket to this performance, was it for a Senior Membership, was it simply a $15 donation?). Is there a way to get even a little bit of that info onto a receipt design? 

  • I could be wrong, but if you want to include performance type information on a RECEIPT (not at ticket), you'll need to change a local stored procedure named LP_TICKET_ELEMENTS. This will allow you to use up to 6 user defined elements on your receipt design.

  • Is the procedure you mentioned in System Tables? Because I am not seeing it listed under the system tables I have access to.

  • You'll need someone with access to SSMS (SQL Server Management Studio). Here is the reference to the stored procedure within the Help System.

    Tessitura v15 Help System - User Defined Data Elements (tessituranetwork.com)

  • Here is where the various data elements reside. It tells you what tables to look at for the desired data. It will help with modifying the lp_ticket_elements stored procedure. The kicker is that you only have a total of 6 data elements, so plan wisely.

    Tessitura v15 Help System - Ticket Design Elements (tessituranetwork.com)

  • Is there any other way of doing it without a customization. We are doing our v16 switch soon and the less customizations we have the easier that transition will be. 

  • Hi Chelsea, 

    We switched to V16 a few months ago and use the data elements to list out the performance date/name on our receipts.  It was not affected by the upgrade (since I think the upgrade most heavily touches Membership and Contribution tables).  

    It might be worth giving it a shot if someone in your org who has access to SSMS can pull up that procedure.

  • Thank you for the advice. I think because our original built out process was so bad, my institution is avoiding doing anything that will make our v16 transition any harder.

    I am the one that has access to SSMS, but the last time I tried to build something in it I ended up with a pile of error messages and royally screwed up out TEST environment (thank god it was TEST haha). We are brand new to the system and I do not have a coding background, so I would need a step by step (basically an SSMS for Dummies manual). Does one of those exist for building a customization like this?

  • It just sounds like you need to learn how to update a stored procedure in SSMS. It is not that difficult. I bet you can find a bunch of videos online on how to. I always copy the existing script before I mess with anything so I can always revert back. I always comment out old parts instead of removing. A good ssms skill to develop is to be able to take a stored procedure script and make it a regular ssms query. This will allow you to learn what the procedure is doing and also a way to learn new sql techniques/tricks.

    Another option is to pay Extended Services to do it for you. If you give them the changes you want to make to the script, it is quick for them to modify it in SSMS. You just need to have the new script with your changes and have them modify it for you.

    What is your email? I can send you a Word document with my proposed changes to the LP_TICKET_ELEMENTS procedure. It'll give you a bunch of ideas on what kinds of data you can get onto your receipts. You'll need to factor in how many characters you can fit onto your receipt per line. You can also get data from the 4 text fields from either your performance, production season, or production.

    We didn't end up implementing the changes because we our CRM administrator left and then COVID hit. After COVID, 99% of our orders are done online, so we don't have that issue as often as we used to.

  • I would love it if 99% of our sales went online. We are trying to push for that, but our demographic skews in a certain direction that makes it harder. 

    My email is martic@nbmaa.org. I would appreciate any help and advice you want to give. I'm kind of learning as I go here.